Axios fetch adapter size limit bypass leading to resource exhaustion
CVE-2026-44488 affects Axios, a promise-based HTTP client for browsers and Node.js. In Axios versions 1.7.0 through 1.15.x, the fetch adapter did not enforce configured maxContentLength and maxBodyLength limits. As a result, applications using adapter: 'fetch', or running in environments where Axios selected the fetch adapter automatically, could send or receive bodies larger than the explicitly configured limits. This breaks an expected security boundary around request and response sizing. In server-side usage, exploitation can occur when a malicious or compromised upstream server returns an oversized response, when an attacker can supply a large data: URL, or when an application forwards attacker-controlled request bodies through Axios while relying on maxBodyLength for enforcement. The issue is effectively an uncontrolled resource consumption condition caused by failure to apply configured size restrictions in the fetch adapter path.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.