CVE-2026-67320 is a high-severity information disclosure vulnerability in axios affecting Node.js deployments that use the HTTP adapter. Axios hardens merged request configuration by creating a null-prototype object, but request interceptors execute after the merge step. Common immutable interceptor patterns, including object spread and Object.assign cloning, can convert the hardened configuration back into a regular object. Axios then dispatches that modified configuration without re-hardening it, and the Node.js HTTP adapter reads the proxy setting through the prototype chain. If an attacker is able to pollute Object.prototype with a proxy property, affected requests can be redirected through an attacker-controlled proxy. For plaintext HTTP traffic, this can expose authorization data, request metadata, and request bodies, and it also enables attacker-controlled responses to be returned to the application. The issue is described for axios versions 0.31.1 before 0.33.0 and 1.15.2 before 1.18.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information disclosure/spoofing vulnerability in the Axios HTTP client library for Node.js caused by improper handling of request configuration. Under certain conditions, prior prototype pollution compromise can inject a malicious proxy configuration via the prototype chain, redirecting application requests through an attacker-controlled proxy.
A high-severity axios vulnerability in Node.js HTTP adapter deployments where prototype pollution of Object.prototype.proxy can cause requests to be routed through an attacker-controlled proxy, exposing plaintext HTTP request data and enabling attacker-controlled responses.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.