Prototype Pollution in Axios
CVE-2026-67314
axios versions >=1.15.2 and <1.18.0 contain prototype-pollution read-side gadgets in Basic auth subfield handling (lib/adapters/http.js and lib/helpers/resolveConfig.js). When an application is already affected by a separate prototype-pollution primitive and makes an axios request with an own auth object that omits the username and/or password properties, axios reads the inherited Object.prototype.username and Object.prototype.password values and uses them to construct an outbound 'Authorization: Basic ...' header. axios itself does not pollute prototypes. The practical impact is outbound request tampering: an attacker who controls the polluted prototype values can inject attacker-chosen Basic auth credentials or replace an existing Authorization header. Credential disclosure is only possible under additional application-specific conditions.
Vulnerability class: Prototype Pollution
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L.
EPSS exploit prediction
EPSS 0.004, 35.9th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Axios — versions 1.15.2, 1.18.0
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-xj6q-8x83-jv6g) (vendor-advisory, Exploit, Mitigation, Vendor Advisory)
- VulnCheck Advisory: axios before 1.18.0 Prototype Pollution via auth subfields (Third Party Advisory, third-party-advisory)