CVE-2026-67320
Prototype-pollution in axios HTTP adapter can route requests via attacker-controlled proxy.
Is CVE-2026-67320 being exploited?
Not confirmed. CVE-2026-67320 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-67320?
CVE-2026-67320 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67320?
Yes. A fix has been recorded for CVE-2026-67320. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67320 affect?
CVE-2026-67320 affects axios >=0.31.1, <0.33.0, axios >=1.15.2, <1.18.0, Node.js applications using axios HTTP adapter. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67320?
Upgrade axios to >=0.33.0 or >=1.18.0 and audit for prototype-pollution vectors.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
If Object.prototype.proxy is polluted, attackers can route axios HTTP requests through a malicious proxy, exposing Authorization/basic auth, URL, headers, body and spoof responses.
Patch when possible
- affected>= 0.31.1 and < 0.33.0
- affected>= 1.15.2 and < 1.18.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.