Axios auth prototype pollution in HTTP adapter (v1.15.2-1.17.9)
CVE-2026-67314 Published on August 1, 2026
axios before 1.18.0 Prototype Pollution via auth subfields
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.
Weakness Type
What is a Prototype Pollution Vulnerability?
The software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
CVE-2026-67314 has been classified to as a Prototype Pollution vulnerability or weakness.
Products Associated with CVE-2026-67314
Want to know whenever a new CVE is published for Axios? stack.watch will email you.
Affected Versions
axios:- Version 1.15.2 and below 1.18.0 is affected.
- Version 1.18.0 is unaffected.