Resource exhaustion in Axios
CVE-2026-67318
axios versions >=1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node's HTTP/2 request API does not honor the maxBodyLength option and axios's byte-counting stream wrapper is gated on maxRedirects === 0, an attacker who controls a stream passed to axios can cause the application to transmit outbound data exceeding the configured finite maxBodyLength. Impact is limited to resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control. Calls using the default maxBodyLength: -1 and browser adapters are not affected.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
EPSS exploit prediction
EPSS 0.006, 50.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Axios — versions 1.13.0, 1.18.0
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-mwf2-3pr3-8698) (vendor-advisory, Exploit, Mitigation, Vendor Advisory)
- VulnCheck Advisory: axios 1.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/2 (Third Party Advisory, third-party-advisory)