Skip to main content
Mallory
HighPublic exploit

Axios fetch adapter size limit bypass leading to resource exhaustion

IdentifiersCVE-2026-44488CWE-770· Allocation of Resources Without…

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

The primary impact is availability degradation or denial of service through resource exhaustion. A vulnerable application may process, buffer, or transmit oversized request or response bodies despite configured limits, potentially consuming excessive memory, CPU, and network bandwidth. This is particularly relevant in server-side deployments where Axios is used to fetch untrusted content or proxy attacker-controlled data. No direct confidentiality or integrity impact is described in the provided content.

Mitigation

If you can’t patch tonight, do this now.

Where immediate patching is not possible, avoid using the fetch adapter in security-sensitive server-side contexts where request or response size limits are relied upon. Prefer the Node.js http adapter for server-side requests requiring strict size enforcement. Independently validate and cap attacker-controlled request bodies before passing them to Axios. Reject or strictly allowlist attacker-controlled URL schemes, especially data: URLs, before invoking Axios. Additional upstream response-size controls at proxies or application logic may further reduce exposure.

Remediation

Patch, then assume compromise.

Upgrade Axios to a fixed release that enforces maxContentLength and maxBodyLength in the fetch adapter. The provided advisory states the issue is fixed in Axios 1.16.0 or later; the content also references 0.32.0 as a fixed version for the 0.x line. Apply the appropriate fixed version for the deployed major branch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
AxiosAxiosapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.