Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/axios/axios/security/advisories/GHSA-mwf2-3pr3-8698
- https://www.vulncheck.com/advisories/axios-before-maxbodylength-bypass-via-http-
- https://github.com/axios/axios/security/advisories/GHSA-mwf2-3pr3-8698
FAQ
What is CVE-2026-67318?
CVE-2026-67318 is a documented vulnerability. 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 A...
How severe is CVE-2026-67318?
CVSS scoring is not yet available for CVE-2026-67318. Check NVD for updates.
Is there a patch for CVE-2026-67318?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.