Allocation of Resources Without Limits or Throttling Affecting axios package, versions >=1.7.0 <1.18.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-AXIOS-18065353
- published21 Jul 2026
- disclosed20 Jul 2026
- creditAhmad Sadeddin
Introduced: 20 Jul 2026
NewCVE-2026-67317 (opens in a new tab)How to fix?
Upgrade axios to version 1.18.0 or higher.
Overview
axios is a promise-based HTTP client for the browser and Node.js.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the getBodyLength() and resolveBodyLength() functions of lib/adapters/fetch.js, which lack a branch for WHATWG ReadableStream bodies, so the resolved length is undefined and the pre-dispatch maxBodyLength check is skipped. An attacker who controls a streamed request body can transmit uploads that exceed the configured maxBodyLength, causing unexpected outbound egress and consuming upstream API quota or bandwidth, by supplying a ReadableStream without a reliable Content-Length to a fetch-adapter request. Exploitation requires the fetch adapter, a body-bearing method such as POST, PUT, or PATCH, request data supplied as a ReadableStream without a reliable Content-Length, and a finite maxBodyLength, while the Node HTTP adapter and known-length bodies are unaffected.
Workaround
This vulnerability can be avoided in Node.js by using the HTTP adapter (adapter: "http") for untrusted stream uploads, which enforces the stream body limit that the fetch adapter does not.