CVE-2026-67320 Details
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).
A vulnerability exists in Axios versions 0.31.1 prior to 0.33.0 and 1.15.2 prior to 1.18.0, when used in a Node.js environment with the HTTP adapter. This vulnerability allows for prototype pollution that can be exploited to route HTTP requests through an attacker-controlled proxy. Although Axios attempts to secure merged request configurations by creating a null-prototype object, this hardening is undone by request interceptors that run afterward. Interceptors that use common patterns to clone objects can revert the configuration back to a standard object, which then inherits from the prototype chain. If an attacker has previously polluted the prototype, they can manipulate the proxy configuration, leading to the interception of sensitive request data such as Authorization headers, Basic authentication details, request methods, absolute URLs, Host headers, and request bodies. The proxy can also send its own responses back through Axios, effectively allowing for man-in-the-middle style attacks on the HTTP requests.
Users can upgrade to Axios versions 0.33.0 or 1.18.0, where this vulnerability has been patched. Alternatively, for versions that are not yet upgraded, an own 'proxy: false' can be set on the request or Axios instance. If the Node fetch adapter is an option, it can be used as a replacement for affected requests.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Aug 3, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/axios/axios/commit/df53d7dd99b202fb194217abd127ae6a630e70dc | [email protected] | Patch |
| https://github.com/axios/axios/security/advisories/GHSA-gcfj-64vw-6mp9 | [email protected] | ExploitMitigationVendor Advisory |
| https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-node-http-adapter | [email protected] | PatchThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| axios axios | >= 0.31.1, < 0.33.0 >= 1.15.2, < 1.18.0 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 1, 2026 | Initial Analysis | [email protected] |
| Aug 3, 2026 | CVE Modified | CISA-ADP |
| Aug 1, 2026 | New CVE Received | [email protected] |