Cyber Resilience

CVE-2026-40175

SSRF in Axios ≤ 0.31.0

Public PoCSSRF
Published
10 April 2026
Modified
13 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.019 78th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2026-40175 is a medium-severity HTTP Request/Response Splitting (CWE-113) vulnerability in Axios Axios. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 22% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-40175 affects the Axios library, a promise-based HTTP client used in browsers and Node.js environments, in versions prior to 1.15.0. The vulnerability enables a specific "Gadget" attack chain that escalates Prototype Pollution occurring in any third-party dependency into Remote Code Execution (RCE) or Full Cloud Compromise, including via AWS IMDSv2 bypass. It is associated with CWEs-113, CWE-444, and CWE-918, and carries a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), indicating critical severity.

Remote attackers with network access can exploit this vulnerability with low complexity, no required privileges, and no user interaction. By leveraging Prototype Pollution in a third-party dependency, they can chain it through Axios to achieve RCE on the target system or full compromise of cloud environments, such as bypassing AWS IMDSv2 protections.

The vulnerability is addressed in Axios version 1.15.0. Mitigation involves updating to this patched release, as detailed in the official GitHub security advisory (GHSA-fvcv-3m26-pcqx), the release notes for v1.15.0, and the fixing commit and pull request.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access ControlA05:2025 InjectionA06:2025 Insecure DesignA08:2025 Software or Data Integrity Failures

EU & UK References

Vulnerability Data

Axios is a promise based HTTP client for the browser and Node.js. Versions prior to 1.15.0 and 0.3.1 are vulnerable to a specific gadget-style attack chain in which prototype pollution in a third-party dependency may be leveraged to inject unsanitized…

more

header values into outbound requests. This vulnerability is fixed in 1.15.0 and 0.3.1.

CWE(s)
CWE-113CWE-444CWE-918CWE-915

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1098 Account Manipulation Persistence
Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.
attack.mitre.org →
T1098.001 Additional Cloud Credentials Persistence
Adversaries may add adversary-controlled credentials to a cloud account to maintain persistent access to victim accounts and instances within the environment.
attack.mitre.org →
T1098.003 Additional Cloud Roles Persistence
An adversary may add additional roles or permissions to an adversary-controlled cloud account to maintain persistent access to a tenant.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-42044Same product: Axios Axios
CVE-2026-42033Same product: Axios Axios
CVE-2026-42264Same product: Axios Axios
CVE-2026-44494Same product: Axios Axios
CVE-2026-42041Same product: Axios Axios
CVE-2026-42035Same product: Axios Axios
CVE-2026-44489Same product: Axios Axios
CVE-2025-27152Same product: Axios Axios
CVE-2026-42038Same product: Axios Axios
CVE-2024-39338Same product: Axios Axios

Affected Assets

axios
axios
≤ 0.31.0 · 1.0.0 — 1.15.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.4.2
  • V4.1.3
  • V4.2.4
  • V1.3.6

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces authorizations so that only permitted attributes may be modified on an object.

AC-4 Information Flow Enforcement good match

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

AC-6 Least Privilege good match

Limits the set of modifiable attributes a subject is authorized to touch.

SI-10 Information Input Validation good match

Input validation stops unneutralized CR/LF characters from being accepted and later emitted in HTTP headers.

SI-15 Information Output Filtering good match

Output filtering can neutralize CRLF sequences before they reach HTTP response headers.

SC-7 Boundary Protection partial match

Boundary protection at external interfaces can enforce consistent HTTP request/response parsing rules between intermediaries and endpoints.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Configuration management can enforce uniform HTTP parsing rules across intermediaries, directly mitigating inconsistent interpretation.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input sanitization and header handling that prevent CRLF injection.

DE.CM-01 partial match
prevents

Network monitoring can detect smuggling attempts via anomalous HTTP traffic or logs, while eliminating the inconsistency directly aids detection of such events.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network protections can enforce consistent HTTP proxy/firewall behavior to block smuggling, and removing the weakness helps prevent unauthorized access via request smuggling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards explicitly forbid unsafe dynamic attribute assignment and require property allow-lists.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect CRLF injection flaws before deployment.

A.5.7 Threat intelligence partial match
prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

A.8.20 Networks security partial match
degrades

Network security controls can enforce consistent HTTP parsing and proxy behavior that mitigates request smuggling.

A.8.21 Security of network services partial match
degrades

Secure network services include hardening proxies and gateways against inconsistent HTTP interpretation.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection into HTTP headers.

References