CVE-2026-67320 axios before 0.33.0 Prototype Pollution via Node HTTP adapter
Prototype pollution in axios Node HTTP adapter allows attackers to route requests through malicious proxies, exposing sensitive headers and data.
- 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-67320?
CVE-2026-67320 is a high-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 in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled proxy. axios hardens merged request configuration by creating a null-prototype object, but request interceptors run after the merge; a common immutable interceptor pattern such as {...config} or Object.assign({}, config) converts the hardened config back into a regular object. axios then dispatches that object without re-hardening it, and the Node HTTP adapter reads config.proxy through the prototype chain. If an attacker can pollute Object.prototype.proxy, affected requests can be routed through an attacker-controlled proxy. For plaintext HTTP requests, the proxy can observe Authorization headers, Basic auth from config.auth, method, absolute URL, Host, and request body, and can return its own response. This does not establish browser impact or HTTPS header/body disclosure under normal TLS validation. Affected versions are >=0.31.1 (fixed in 0.33.0) and >=1.15.2 (fixed in 1.18.0).
Weakness: CWE-200
Which versions are affected by CVE-2026-67320?
4 open source packages ship an affected version, including axios. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
axios npm | From 0.31.1 | 0.33.0 |
axios npm | From 0.31.1 | 0.33.0 |
axios npm | From 1.15.2 | 1.18.0 |
axios npm | From 1.15.2 | 1.18.0 |
Products include Axios Axios.
How do I fix CVE-2026-67320?
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-67320 being exploited?
There is no known exploitation of CVE-2026-67320 in the wild and no public exploit code.
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-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
- CVE-2026-44486 Axios: Proxy-Authorization header leaks to redirect target when proxy is re-evaluated to direct connection
Sources
Also known as CLEANSTART-2026-RK13390, CVE-2026-69124, DEBIAN-CVE-2026-67320, ECHO-7df6-530c-722c, GHSA-gcfj-64vw-6mp9, MINI-3fc3-x7qc-x2q5 and 17 more.