CVE-2026-67318: axios 1.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/2
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
axiosto a version that resolves this vulnerability.Fixed in 1.18.0 - Compensating control
Mitigate the maxBodyLength bypass by not sending streamed requests with Node.js HTTP adapter using httpVersion: 2 (use HTTP/1.1, since browser adapters and default maxBodyLength (-1) are stated as not affected).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67318?
CVE-2026-67318 has a risk rating of 19.
How do I fix CVE-2026-67318?
To mitigate CVE-2026-67318, update axios to version 1.18.0 or later.
Which versions of axios are affected by CVE-2026-67318?
CVE-2026-67318 affects axios versions 1.13.0 through 1.17.0.
What exploit does CVE-2026-67318 allow?
CVE-2026-67318 allows a maxBodyLength bypass when using HTTP/2 in axios.
What component is primarily affected by CVE-2026-67318?
The Node.js HTTP adapter in axios is primarily affected by CVE-2026-67318.