npm
CVE-2026-67318
Axios: HTTP/2 streamed uploads bypass `maxBodyLength`
- Severity
- Medium
- Published
- 20 Jul 2026
- Last changed
- 10 Sept 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 1.18.0
- Exploit chance
- 0.6% in the next 30 daysHigher than 50% of CVEs. EPSS by FIRST, 19 Nov 2026
- Also known as
- GHSA-mwf2-3pr3-8698
- Sources
- OSV.dev and GitHub
Description
Axios versions with Node.js HTTP/2 support allow streamed request bodies to bypass maxBodyLength enforcement when requests are sent with httpVersion: 2.
This affects applications that rely on maxBodyLength as a hard cap while forwarding attacker-controlled streams, such as upload endpoints proxying user data to an upstream HTTP/2 service. Buffered request bodies are still checked before the request is sent.
An attacker who can control a stream passed to axios can cause the application to transmit more outbound data than the configured maxBodyLength limit.
Practical impact is limited to resource consumption and policy bypass: excess outbound bandwidth, egress cost, upstream quota consumption, and limited availability impact on the application or upstream peer. This does not provide code execution, credential disclosure, or request destination control.
Workarounds
For axios >=1.15.1, set maxRedirects: 0 on affected HTTP/2 streamed upload calls. HTTP/2 redirects are not currently supported by the axios HTTP/2 adapter, so this is a practical per-call mitigation for this path.
For earlier affected versions, pre-limit the stream with a byte-counting transform before passing it to axios, reject oversized uploads before forwarding them, or avoid httpVersion: 2 for untrusted streamed uploads.### Summary On Node.js, axios's maxBodyLength is documented as a hard cap on outbound request bodies.
Affected software
| Software | Affected versions |
|---|---|
axiosnpm · osv:npm:axios |
|
About axios
- Weekly downloads (npm)
- 143,624,637npm, 16 Nov 2026
Vulnerabilities in axios
- In our list
- 35
- Published in the last 12 months
- 35
- Critical, last 12 months
- 0
- High, last 12 months
- 13
- Known exploited
- 0
- CVE-2026-101904Axios: Header Injection via Inherited headers After Minimal InterceptorMedium 30 Sept 2026
- CVE-2026-101900Axios: Fetch Adapter Header Injection via Inherited FormData getHeadersMedium 30 Sept 2026
- CVE-2026-101908Axios: Prototype pollution gadget in fetch adapter can alter outbound requestsMedium 30 Sept 2026
- CVE-2026-101902Axios: Prototype-Pollution Gadget in the Default Instance Allows Inherited Object.prototype.method to Override HTTP MethodMedium 30 Sept 2026
- CVE-2026-101898Axios: HTTP/2 adapter bypasses configured DNS lookup and proxy controlsHigh 30 Sept 2026
- CVE-2026-101901Axios: Denial of Service via Unhandled 'error' Event in HTTP/2 ClientHttp2Session InitializationHigh 30 Sept 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67318
- GitHub Advisory Database https://github.com/advisories/GHSA-mwf2-3pr3-8698