https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 06:55:02 +0000 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0698 certfr-2026-avi-0698 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0698 https://cve.radiocsirt.org/vuln/cleanstart-2026-be61221 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: opensearch-dashboards-fips</p> <p>Multiple security vulnerabilities affect the opensearch-dashboards-fips package. These issues are resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: opensearch-dashboards-fips</p> <p>Multiple security vulnerabilities affect the opensearch-dashboards-fips package. These issues are resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-be61221 https://cve.radiocsirt.org/vuln/euvd-2026-292960 EUVD-2026-292960 https://cve.radiocsirt.org/vuln/euvd-2026-292960 https://cve.radiocsirt.org/vuln/fkie_cve-2026-42036 <p>Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, 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. This vulnerability is fixed in 1.15.1 and 0.31.1.</p> <p>Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, 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. This vulnerability is fixed in 1.15.1 and 0.31.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-42036 https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/ghsa-vf2m-468p-8v99 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-42036 <p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: node-axios, Ubuntu:Pro:22.04:LTS: node-axios, Ubuntu:Pro:24.04:LTS: node-axios, Ubuntu:25.10: node-axios, Ubuntu:Pro:26.04:LTS: node-axios</p> <p>Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, 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. This vulnerability is fixed in 1.15.1 and 0.31.1.</p> <p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: node-axios, Ubuntu:Pro:22.04:LTS: node-axios, Ubuntu:Pro:24.04:LTS: node-axios, Ubuntu:25.10: node-axios, Ubuntu:Pro:26.04:LTS: node-axios</p> <p>Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, 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. This vulnerability is fixed in 1.15.1 and 0.31.1.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-42036 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1450 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, wodurch weitere Angriffe möglich werden.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, wodurch weitere Angriffe möglich werden.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1450