CVE-2026-67314
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| axios | axios | 1.15.2 < 1.18.0 | affected |
| axios | axios | 1.18.0 | unaffected |
Weaknesses
- CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
References
- https://github.com/axios/axios/security/advisories/GHSA-xj6q-8x83-jv6g
- https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-auth-subfields
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.