Is this vulnerability directly exploitable through Axios alone?

No. Axios acts as a gadget in a larger attack chain. Exploitation typically requires a separate Prototype Pollution vulnerability that allows an attacker to corrupt objects used as Axios configuration, which can then be leveraged for SSRF and further escalation.

What level of access does an attacker need?

An attacker generally needs the ability to influence request-related data or to trigger a Prototype Pollution issue in the application or its dependencies. With that, they can shape Axios' behavior to target internal services or metadata endpoints from the compromised service.

What is the safest general fix pattern?

Architect your Axios usage so that it never consumes polluted or mixed-trust configuration: construct new, minimal config objects for each request, validate and normalize URLs and headers, and enforce strict allowlists for outbound destinations. Combine this with network-level controls that prevent access to metadata services and sensitive internal endpoints.

Severity:

CRITICAL RISK

(10.0)

Server-Side Request Forgery & Header Injection Gadget Chain (CWE-918, CWE-113) in Axios HTTP Client

CVE-2026-40175

Published:

Apr 10, 2026

Status:

Undergoing Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Server-Side Request Forgery and HTTP Header Manipulation Gadget Chain

CWE:

CWE-113;CWE-444;CWE-918

Impact:

Remote Code Execution and Cloud Instance Compromise

Severity:

CRITICAL RISK

(10.0)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery and HTTP Header Manipulation Gadget Chain

CWE:

CWE-113;CWE-444;CWE-918

Impact:

Remote Code Execution and Cloud Instance Compromise

Severity:

CRITICAL RISK

(10.0)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Server-Side Request Forgery & Header Injection Gadget Chain (CWE-918, CWE-113) in Axios HTTP Client

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal