Prototype Pollution in Axios
CVE-2026-67319
axios before 0.33.0 (and 1.x before 1.18.0) can consume inherited properties from nested request option objects when the JavaScript process's Object.prototype has already been polluted by another component. While the top-level merged config uses a null prototype, nested plain objects such as auth and paramsSerializer are cloned into ordinary objects and read without own-property checks. When an application passes placeholder nested objects such as auth: {} or paramsSerializer: {}, inherited username/password values can cause silent injection of an Authorization: Basic header, and inherited encode/serialize values can alter query-string serialization (full serializer replacement requires a function-valued pollution primitive). This is exploitable only in the presence of pre-existing prototype pollution.
Vulnerability class: Prototype Pollution
Published · last modified .
CVSS v3 metric
CVSS v3 base score 3.7 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS 0.003, 25.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Axios — versions 0.8.0, 0.33.0, 1.0.0
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-7q8q-rj6j-mhjq) (vendor-advisory, Exploit, Mitigation, Vendor Advisory)
- VulnCheck Advisory: axios before 0.33.0 Prototype Pollution via nested option objects (Third Party Advisory, third-party-advisory)