CVE-2026-42033
Axios ≤ 0.31.1
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-42033 is a high-severity Prototype Pollution (CWE-1321) vulnerability in Axios Axios. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 46% 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-6 (Least Privilege) — 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-42033 is a prototype pollution vulnerability in Axios, a promise-based HTTP client used in browsers and Node.js environments. In versions prior to 1.15.1 and 0.31.1, Axios lacks a hasOwnProperty guard when reading keys from Object.prototype, allowing pollution by co-dependencies to compromise its internal state. This leads to two primary impacts: silent interception and modification of JSON responses before they reach the application, or full hijacking of the underlying HTTP transport layer.
Exploitation requires an attacker to first achieve prototype pollution on Object.prototype from a separate source within the same process, such as a vulnerable co-dependency. A remote attacker with no privileges can then leverage this precondition over the network, though it demands high attack complexity. Successful exploitation grants high confidentiality and integrity impacts, enabling the attacker to alter all JSON responses or access sensitive request details including credentials, headers, and body content.
The official GitHub security advisory (GHSA-pf86-5x62-jrwf) confirms the issue and states that it is fully remediated in Axios versions 1.15.1 and 0.31.1, recommending immediate upgrades to these or later versions as the primary mitigation. Affected users should audit dependencies for prototype pollution risks and review co-libraries for similar issues.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25588
Vulnerability Data
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, when Object.prototype has been polluted by any co-dependency with keys that axios reads without a hasOwnProperty guard, an attacker can (a) silently intercept…
more
and modify every JSON response before the application sees it, or (b) fully hijack the underlying HTTP transport, gaining access to request credentials, headers, and body. The precondition is prototype pollution from a separate source in the same process. This vulnerability is fixed in 1.15.1 and 0.31.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.3.6
Mitigating Controls (NIST 800-53 r5) AI
Enforces authorizations so that only permitted attributes may be modified on an object.
Limits the set of modifiable attributes a subject is authorized to touch.
Validates incoming attribute names and values so that only explicitly allowed fields are accepted for update.
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.
Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.
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.
Secure coding standards explicitly forbid unsafe dynamic attribute assignment and require property allow-lists.
Security testing in development catches prototype-pollution flaws before release.
Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.
Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.
Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.
Information access restriction limits who can modify objects but does not address which attributes may be changed.