Cyber Resilience

CVE-2026-44489

Axios 1.15.2

Public PoC
Published
11 June 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2026-44489 is a low-severity HTTP Request/Response Splitting (CWE-113) vulnerability in Axios Axios. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 14th percentile by exploit likelihood (below the median); 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 SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Axios is a promise based HTTP client for the browser and Node.js. From 1.15.2 to before 1.16.0, nested objects created by utils.merge() (e.g., config.proxy) are still constructed as plain {} with Object.prototype in their chain. The setProxy() function at lib/adapters/http.js:209-223…

more

reads proxy.username, proxy.password, and proxy.auth without hasOwnProperty checks. When Object.prototype.username is polluted, setProxy() constructs a Proxy-Authorization header with attacker-controlled credentials and injects it into every proxied HTTP request. This vulnerability is fixed in 1.16.0.

CWE(s)

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.
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.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-42035Same product: Axios Axios
CVE-2026-44490Same product: Axios Axios
CVE-2026-42040Same product: Axios Axios
CVE-2026-42044Same product: Axios Axios
CVE-2026-42264Same product: Axios Axios
CVE-2026-42033Same product: Axios Axios
CVE-2026-44494Same product: Axios Axios
CVE-2026-42041Same product: Axios Axios
CVE-2026-42037Same product: Axios Axios
CVE-2026-40175Same product: Axios Axios

Affected Assets

axios
axios
1.15.2

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
  • V1.3.6
  • V4.2.3

Mitigating Controls (NIST 800-53 r5) AI

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

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

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-06 mostly match
prevents

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

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.

finds

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

prevents

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

prevents

Application security requirements explicitly call for controls against injection flaws including HTTP header manipulation.

prevents

Secure architecture principles reduce the likelihood of header-splitting vulnerabilities through proper component isolation.

prevents

Secure coding standards require neutralization of CRLF sequences before inclusion in HTTP headers.

prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References