What’s Vulnerable › Vulnerabilities
CVE-2026-67318: axios 1.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/2
- Severity: medium (CVSS 5.3 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.6% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2026-08-01 · updated 2026-09-01
- Weakness: CWE-400
Description
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 products
- axios: from 1.13.0 before 1.18.0 — fixed in 1.18.0
How to fix
Upgrade to a fixed version: axios 1.18.0. Check the vendor advisory for mitigations.
References
- https://github.com/axios/axios/security/advisories/GHSA-mwf2-3pr3-8698
- https://www.vulncheck.com/advisories/axios-before-maxbodylength-bypass-via-http-2
- https://github.com/axios/axios/security/advisories/GHSA-mwf2-3pr3-8698
Get alerted when CVE-2026-67318 or the next vulnerability affects your stack