PatchSiren cyber security CVE debrief
CVE-2026-44495 axios CVE debrief
Axios, a promise-based HTTP client for the browser and Node.js, contains prototype-pollution gadgets in request config processing from versions 0.19.0 to before 0.31.1 and 1.15.2. If another vulnerability in the same JavaScript process has already polluted Object.prototype.transformResponse, affected Axios versions may treat that inherited value as request configuration or as an option validator. Axios does not itself create the prototype pollution; exploitability requires a separate prototype-pollution vulnerability or equivalent attacker control over Object.prototype before Axios creates a request. This vulnerability is fixed in 0.31.1 and 1.15.2.
- Vendor
- axios
- Product
- Unknown
- CVSS
- HIGH 7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-06-11
- Advisory updated
- 2026-09-11
Who should care
Defenders responsible for JavaScript environments, especially those using Axios within the specified vulnerable ranges, should assess exposure and prioritize verification and mitigation efforts.
Why it matters
CVE-2026-44495 is a high-severity vulnerability in Axios that could allow attackers to manipulate request configurations or validation options through prototype pollution. Defenders should verify exposure, prioritize patching, and monitor for potential impacts.
- Potential for attackers to inject malicious properties into Object.prototype, allowing for request configuration manipulation or option validation abuse.
- Requires verification of Axios versions and assessment of separate prototype-pollution vulnerabilities or equivalent attacker control.
- Prioritization of patching or updating Axios to versions 0.31.1 or 1.15.2, or later.
- Monitoring for potential impacts on systems and applications using affected Axios versions.
Technical summary
Axios, a promise-based HTTP client for the browser and Node.js, contains prototype-pollution gadgets in request config processing from versions 0.19.0 to before 0.31.1 and 1.15.2. If another vulnerability in the same JavaScript process has already polluted Object.prototype.transformResponse, affected Axios versions may treat that inherited value as request configuration or as an option validator. This vulnerability is fixed in 0.31.1 and 1.15.2. Defenders should prioritize verifying exposure in JavaScript environments using Axios within the specified vulnerable ranges and assess the feasibility of separate prototype-pollution vulnerabilities or equivalent attacker control.
Defensive priority
Defenders should prioritize verifying exposure in JavaScript environments using Axios within the specified vulnerable ranges and assess the feasibility of separate prototype-pollution vulnerabilities or equivalent attacker control.
Recommended defensive actions
- Verify Axios versions in use and compare them to the vulnerable ranges (0.19.0 to before 0.31.1 and 1.15.2).
- Assess the JavaScript environment for potential separate prototype-pollution vulnerabilities or equivalent attacker control.
- Apply patches or updates to Axios versions 0.31.1 or 1.15.2, or later, as available.
- Monitor for and address potential impacts on systems and applications using affected Axios versions.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
Axios contains prototype-pollution gadgets in request config processing from versions 0.19.0 to before 0.31.1 and 1.15.2. The CVE and NVD records provide details on the vulnerability, its impact, and affected versions. Vendor advisories and third-party errata offer additional context and potential mitigations. Defenders should verify exposure in JavaScript environments using Axios within the specified vulnerable ranges and assess the feasibility of separate prototype-pollution vulnerabilities or equivalent attacker control.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-44495 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-44495
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-44495 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-44495
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/axios/axios/security/advisories/GHSA-3g43-6gmg-66jw
[email protected] - Exploit, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:20889
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:20938
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:27044
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:27063
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:27944
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:28964
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:29082
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.