CVE-2026-67316: axios before 1.18.0 Prototype Pollution via bodyless methods
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
axiosto a version that resolves this vulnerability.Fixed in 1.18.0 - Upgrade
Upgrade
axiosto a version that resolves this vulnerability.Fixed in 0.33.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67316?
CVE-2026-67316 has a risk score of 37, indicating a moderate level of vulnerability.
How do I fix CVE-2026-67316?
To fix CVE-2026-67316, upgrade axios to version 1.18.0 or later.
What causes CVE-2026-67316?
CVE-2026-67316 is caused by prototype pollution via bodyless methods in axios that can manipulate request construction.
Which versions of axios are affected by CVE-2026-67316?
All versions of axios prior to 1.18.0 are affected by CVE-2026-67316.
Can CVE-2026-67316 lead to a security breach?
Yes, CVE-2026-67316 can potentially lead to security breaches if exploited by modifying the prototype of objects used in requests.