Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| axios | axios | >= 1.15.2, < 1.18.0 |
References
- https://github.com/axios/axios/security/advisories/GHSA-xj6q-8x83-jv6gExploit, Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-auth-subfieldsThird Party Advisory
- https://github.com/axios/axios/security/advisories/GHSA-xj6q-8x83-jv6gExploit, Mitigation, Vendor Advisory
Timeline
- Published
- Aug 1, 2026
- Last modified
- Sep 1, 2026
- NVD status
- Analyzed