CVE-2026-67320PoC(axios / axios)

LOWCVSS 7.5 · HIGH

Exploit discussion active in current signal (2 latest mentions)

Immediate actions

Hunt for exploitation attempts and persistence artifacts
Increase monitoring for publicly documented tradecraft
Track advisory updates for patch or workaround availability

Recommended action window: High priority (within 72h)

NVD 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).

axios CVEs Back to dashboard

1.5/ 10 priority

Sources & remediation

Patch / fix

Exploit / PoC references

https://github.com/axios/axios/security/advisories/GHSA-gcfj-64vw-6mp9

Weakness type (CWE)

CWE-200

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

axios

Threat summary

Public PoC is present in monitored signal
3 mentions across 2 observed days
Momentum state: stable

What's happening

PoC mentioned or linked in 2 signals
Technical details provided in 3 signals
Disclosure: 1 classified signal
Peaked at 2 mentions on most recent observed day (2026-08-03)
3 total mentions across 2 days

Affected systems

Vendors

axios

Products

axios

Deep dive

Activity timeline3 mentions / 2d

Signal classification2 categories

PoC

266.7%

Disclosure

133.3%

Referenced assets2 URLs

By indicator

Classification over time

Date	Total	Labels

2026-08-01	1	Disclosure1
2026-08-03	2	PoC2

Full discourse3 posts

Hephaestvs@Vulcanux_44d
PoC
csirt_it: ‼️ #PoC #Axios: disponibile Proof of Concept (PoC) per lo sfruttamento della CVE-2026-67320 Rischio: 🔴 Tipologia: 🔸 Information Disclosure 🔸 Spoofing 🔗 https://www.acn.gov.it/portale/w/disponibile-poc-per-lo-sfruttamento-della-cve-2026-67320-nella-libreria-axios ⚠️ Importante mantenere aggiornati i sistemi https://t.co/AFVbjd9hGd
Post summary
The post announces a publicly available proof of concept for CVE‑2026‑67320 affecting the Axios library, noting its information disclosure and spoofing aspects, but provides no evidence of active exploitation, patch, or detailed exploit code.
0000042
629 followersView on X
Hephaestvs@Vulcanux_44d
PoC
csirt_it: ‼️ #PoC #Axios: Disponibile Proof of Concept (PoC) per le vulnerabilità identificate dalle CVE-2026-67320 Rischio: 🔴 Tipologia: 🔸 Information Disclosure 🔸 Spoofing 🔗 https://www.acn.gov.it/portale/w/disponibile-poc-per-lo-sfruttamento-della-cve-2026-67320-nella-libreria-axios ⚠️ Importante mantenere aggiornati i sistemi https://x.com/csirt_it/status/2084278222414340289/photo/1
Post summary
A PoC for CVE-2026-67320 targeting the Axios library has been published, indicating Information Disclosure and Spoofing weaknesses, but there is no evidence of active exploitation or a patch update reported.
0000037
629 followersView on X
Upwind Security MDR@UpwindMDR46d
Disclosure
🚨HIGH - Axios Node.js HTTP Adapter Proxy Hijack via Prototype Pollution (CVE-2026-67320) In axios on Node.js using the HTTP adapter, if Object.prototype is polluted with proxy, immutable-style request interceptors can turn a null-prototype config back into a normal object so the adapter reads config.proxy via the prototype chain and routes traffic through an attacker proxy. Plain HTTP can leak Authorization/basic auth/metadata/body and allow response spoofing; HTTPS is largely constrained by TLS validation. 👉Affected: axios (Node.js HTTP adapter)
Post summary
The message announces a high‑severity vulnerability (CVE‑2026‑67320) in Axios’s Node.js HTTP adapter, detailing how prototype pollution can hijack proxy settings and facilitate credential leakage via plain HTTP.
0000085
278 followersView on X

CPE platform detail1 entries

Part:

Vendor:

Product:

Version:

Target SW:

Target HW:

1 of 1 entries

Part	Vendor	Product	Version	Target SW	Target HW
App	axios	axios	-	node.js	-

Explore more

Back to dashboard axios CVEs axios vulnerabilities

What researchers are saying

CVE-2026-67320

Upwind Security MDR[verified]@UpwindMDRDisclosure

The message announces a high‑severity vulnerability (CVE‑2026‑67320) in Axios’s Node.js HTTP adapter, detailing how prototype pollution can hijack proxy settings and facilitate credential leakage via plain HTTP.

Hephaestvs@Vulcanux_PoC

The post announces a publicly available proof of concept for CVE‑2026‑67320 affecting the Axios library, noting its information disclosure and spoofing aspects, but provides no evidence of active exploitation, patch, or detailed exploit code.

Hephaestvs@Vulcanux_PoC

A PoC for CVE-2026-67320 targeting the Axios library has been published, indicating Information Disclosure and Spoofing weaknesses, but there is no evidence of active exploitation or a patch update reported.