Loading vulnerability details...
When responseType: 'stream' is used, Axios returns the response stream without enforcing maxContentLength. This bypasses configured response-size limits and allows unbounded downstream consumption.
In lib/adapters/http.js:
So callers may set maxContentLength and still receive/read arbitrarily large streamed responses.
Environment:
Steps:
Observed:
Control check:
Type: DoS / unbounded response processing. Impacted: Node.js applications relying on maxContentLength as a safety boundary while using streamed Axios responses.
When responseType: 'stream' is used, Axios returns the response stream without enforcing maxContentLength. This bypasses configured response-size limits and allows unbounded downstream consumption.
In lib/adapters/http.js:
So callers may set maxContentLength and still receive/read arbitrarily large streamed responses.
Environment:
Steps:
Observed:
Control check:
Type: DoS / unbounded response processing. Impacted: Node.js applications relying on maxContentLength as a safety boundary while using streamed Axios responses.
This medium-severity vulnerability could be exploited under certain conditions to compromise security controls or access sensitive information. Should be addressed in a timely manner.
Probability of exploitation in the next 30 days · more likely than 39.6% of all CVEs.
Apply security patches to version 1.15.1, 0.31.1 immediately
Isolate affected systems from untrusted networks until patching is complete
Implement enhanced monitoring for exploitation attempts and unusual behavior