https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 18:23:29 +0000 https://vulnerability.circl.lu/vuln/ghsa-vf2m-468p-8v99 <p><strong>Affected:</strong> npm: axios</p> <p>### Summary</p> <p>When responseType: &#39;stream&#39; is used, Axios returns the response stream without enforcing maxContentLength. This bypasses configured response-size limits and allows unbounded downstream consumption.</p> <p>### Details In lib/adapters/http.js: - 786-789: for responseType === &#39;stream&#39;, Axios immediately settles with the stream. - 797-810: maxContentLength enforcement exists only in the non-stream buffering branch.</p> <p>So callers may set maxContentLength and still receive/read arbitrarily large streamed responses.</p> <p>### PoC</p> <p>Environment: - Axios main at commit f7a4ee2 - Node v24.2.0</p> <p>Steps:</p> <p>1. Start an HTTP server that returns a 2 MiB response body. 2. Call Axios with: - adapter: &#39;http&#39; - responseType: &#39;stream&#39; - maxContentLength: 1024 3. Read the returned stream fully.</p> <p>Observed: - Success; full 2097152 bytes readable.</p> <p>Control check: - Same endpoint with responseType: &#39;text&#39; and same maxContentLength: rejected with maxContentLength size of 1024 exceeded.</p> <p>### Impact Type: DoS / unbounded response processing. Impacted: Node.js applications relying on maxContentLength as a safety boundary while using streamed Axios responses.</p> <p><strong>Affected:</strong> npm: axios</p> <p>### Summary</p> <p>When responseType: &#39;stream&#39; is used, Axios returns the response stream without enforcing maxContentLength. This bypasses configured response-size limits and allows unbounded downstream consumption.</p> <p>### Details In lib/adapters/http.js: - 786-789: for responseType === &#39;stream&#39;, Axios immediately settles with the stream. - 797-810: maxContentLength enforcement exists only in the non-stream buffering branch.</p> <p>So callers may set maxContentLength and still receive/read arbitrarily large streamed responses.</p> <p>### PoC</p> <p>Environment: - Axios main at commit f7a4ee2 - Node v24.2.0</p> <p>Steps:</p> <p>1. Start an HTTP server that returns a 2 MiB response body. 2. Call Axios with: - adapter: &#39;http&#39; - responseType: &#39;stream&#39; - maxContentLength: 1024 3. Read the returned stream fully.</p> <p>Observed: - Success; full 2097152 bytes readable.</p> <p>Control check: - Same endpoint with responseType: &#39;text&#39; and same maxContentLength: rejected with maxContentLength size of 1024 exceeded.</p> <p>### Impact Type: DoS / unbounded response processing. Impacted: Node.js applications relying on maxContentLength as a safety boundary while using streamed Axios responses.</p> https://vulnerability.circl.lu/vuln/ghsa-vf2m-468p-8v99