CVE-2026-67316 axios before 1.18.0 Prototype Pollution via bodyless methods
Prototype pollution in axios allows attackers to manipulate request construction, potentially sending unintended bodies or routing traffic through malicious proxies.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-67316?
CVE-2026-67316 is a medium-severity unsafe deserialization vulnerability in axios, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-1321
Which versions are affected by CVE-2026-67316?
4 open source packages ship an affected version, including axios. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
axios npm | All versions | 0.33.0 |
axios npm | All versions | 0.33.0 |
axios npm | From 1.0.0 | 1.18.0 |
axios npm | From 1.0.0 | 1.18.0 |
Products include Axios Axios.
How do I fix CVE-2026-67316?
Upgrade axios to a fixed version for your release line: 0.33.0 or 1.18.0.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-67316 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67316 exists.
Other vulnerabilities in axios
- CVE-2026-44494 Axios: Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`
- CVE-2026-44492 axios's shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)
- CVE-2026-67320 axios before 0.33.0 Prototype Pollution via Node HTTP adapter
- CVE-2026-44487 Axios: Proxy-Authorization Credential Leak to Origin Server Across HTTP-to-HTTPS Redirect in Axios Node.js HTTP Adapter
- CVE-2025-27152 Possible SSRF and Credential Leakage via Absolute URL in axios Requests
Sources
Also known as CLEANSTART-2026-RH17623, CLSA-2026-1784943218, CLSA-2026-1784943302, CLSA-2026-1784943417, CLSA-2026-1785117469, CVE-2026-68944 and 31 more.