Prototype Pollution in Axios
CVE-2026-67316
axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via (config || {}).data before config normalization, causing an attacker-controlled body to be sent on requests that did not set one. Additional low-level paths, only reachable when calling exported adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in axios 1.18.0 and 0.33.0.
Vulnerability class: Prototype Pollution
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.4 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
EPSS 0.004, 37.2th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Axios — versions 1.0.0, 1.18.0, 0
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-mmx7-hfxf-jppx) (vendor-advisory, Exploit, Mitigation, Vendor Advisory)
- VulnCheck Advisory: axios before 1.18.0 Prototype Pollution via bodyless methods (Third Party Advisory, third-party-advisory)