Loading vulnerability…
CVE-2026-67320 affects Axios versions >=0.31.1 and <0.33.0, and >=1.15.2 and <1.18.0, in Node.js deployments using the HTTP adapter. Axios merges request configuration into a null-prototype object, but request interceptors execute afterward. Interceptors using object spread or Object.assign({}, config) can recreate the configuration as a regular prototype-bearing object. Axios dispatches this object without re-hardening it, and the HTTP adapter reads config.proxy through the prototype chain. An attacker with a separate capability to pollute Object.prototype.proxy can consequently redirect affected requests through an attacker-controlled proxy. For plaintext HTTP, this enables disclosure of credentials and request data, as well as forged responses. Browser impact and HTTPS header or body disclosure under normal TLS validation are not established.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A network-accessible vulnerability requiring no privileges or user interaction. The supplied CVSS vectors indicate high confidentiality impact; CVSS v4 additionally indicates low integrity impact and an exploitation prerequisite. The affected product and underlying flaw are not identified. Exploits are available, and a patch publication date of September 28, 2026 is listed.
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.
A prototype-pollution hardening bypass in Axios's Node.js HTTP adapter. A polluted inherited Object.prototype.proxy value can be used after a request interceptor returns a normal object clone, causing HTTP requests to be routed through an attacker-controlled proxy and exposing plaintext request credentials, metadata, and bodies.
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.