# Axios Node HTTP adapter proxy injection via prototype pollution

Source: https://junglewise.ai/threats/axios-node-http-adapter-proxy-injection-via-prototype-pollution-ce5dbbad  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-01. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

Severity: high · CVSS 7.5 · Published 2026-08-01

Axios is a popular HTTP client library used by Node.js applications to make web requests. A vulnerability allows attackers who can pollute the JavaScript Object prototype to redirect HTTP requests through a malicious proxy server. The proxy can intercept sensitive data like authentication tokens, request content, and other metadata from plaintext HTTP traffic. This attack requires the application to use request interceptors (a common pattern) and relies on prior prototype pollution, but the impact is significant for applications handling sensitive data.

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** High severity, with a CVSS score of 7.5, published 1 August 2026.

**Which products and versions are affected?** axios axios >=0.31.1, <0.33.0 and >=1.15.2, <1.18.0.

**Is there a fix for This vulnerability?** A patch was published on 2026-<UNKNOWN>: Fixed in versions 0.33.0 and 1.18.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is This vulnerability attacked?** It is attacked over the network, in a software library.

**Am I affected?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a prototype pollution bypass in Axios's Node.js HTTP adapter. Axios creates a null-prototype object when merging request config to prevent prototype pollution, but request interceptors run after this merge and commonly return a cloned config as a regular object (e.g., using {...config} or Object.assign). The dispatched config is not re-hardened, allowing the HTTP adapter to read config.proxy through the prototype chain. If an attacker has polluted Object.prototype.proxy elsewhere in the process, the request is routed through the attacker's proxy. For plaintext HTTP requests, this discloses Authorization headers, Basic auth credentials, method, URL, Host header, and request body. The attack is limited to Node.js HTTP adapter usage and does not affect HTTPS headers under normal TLS validation. Affected versions are ≥0.31.1 (fixed in 0.33.0) and ≥1.15.2 (fixed in 1.18.0); users should upgrade immediately.

## Affected products

- axios axios >=0.31.1, <0.33.0 and >=1.15.2, <1.18.0

## Timeline

- 2026-07-06: disclosed: Original advisory GHSA-gcfj-64vw-6mp9 published
- 2026-08-01: advisory: Duplicate advisory GHSA-68jp-44vc-2x5h published
- 2026-<UNKN: patched: Fixed in versions 0.33.0 and 1.18.0
- 2026-09-01: other: Duplicate advisory withdrawn; references preserved

## References

- [https://github.com/axios/axios/security/advisories/GHSA-gcfj-64vw-6mp9](https://github.com/axios/axios/security/advisories/GHSA-gcfj-64vw-6mp9)
- [https://github.com/axios/axios/commit/df53d7dd99b202fb194217abd127ae6a630e70dc](https://github.com/axios/axios/commit/df53d7dd99b202fb194217abd127ae6a630e70dc)
- [https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-node-http-adapter](https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-node-http-adapter)