https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 22:24:58 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-12593 bdu:2025-12593 https://cve.radiocsirt.org/vuln/bdu:2025-12593 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0903 certfr-2025-avi-0903 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0903 https://cve.radiocsirt.org/vuln/cleanstart-2026-by06719 <p><strong>Affected:</strong> CleanStart: apache-hive, CleanStart: incubator-kie-kogito-data-index-ephemeral, CleanStart: kogito-apps, CleanStart: stargate, CleanStart: strimzi-kafka-operator, CleanStart: wavefront-proxy</p> <p>CVE-2025-58056 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: apache-hive, CleanStart: incubator-kie-kogito-data-index-ephemeral, CleanStart: kogito-apps, CleanStart: stargate, CleanStart: strimzi-kafka-operator, CleanStart: wavefront-proxy</p> <p>CVE-2025-58056 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-by06719 https://cve.radiocsirt.org/vuln/euvd-2026-252100 EUVD-2026-252100 https://cve.radiocsirt.org/vuln/euvd-2026-252100 https://cve.radiocsirt.org/vuln/fkie_cve-2025-58056 <p>Netty is an asynchronous event-driven network application framework for development of maintainable high performance protocol servers and clients. In versions 4.1.124.Final, and 4.2.0.Alpha3 through 4.2.4.Final, Netty incorrectly accepts standalone newline characters (LF) as a chunk-size line terminator, regardless of a preceding carriage return (CR), instead of requiring CRLF per HTTP/1.1 standards. When combined with reverse proxies that parse LF differently (treating it as part of the chunk extension), attackers can craft requests that the proxy sees as one request but Netty processes as two, enabling request smuggling attacks. This is fixed in versions 4.1.125.Final and 4.2.5.Final.</p> <p>Netty is an asynchronous event-driven network application framework for development of maintainable high performance protocol servers and clients. In versions 4.1.124.Final, and 4.2.0.Alpha3 through 4.2.4.Final, Netty incorrectly accepts standalone newline characters (LF) as a chunk-size line terminator, regardless of a preceding carriage return (CR), instead of requiring CRLF per HTTP/1.1 standards. When combined with reverse proxies that parse LF differently (treating it as part of the chunk extension), attackers can craft requests that the proxy sees as one request but Netty processes as two, enabling request smuggling attacks. This is fixed in versions 4.1.125.Final and 4.2.5.Final.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-58056 https://cve.radiocsirt.org/vuln/ghsa-fghv-69vj-qj49 <p><strong>Affected:</strong> Maven: io.netty:netty-codec-http</p> <p>## Summary A flaw in netty&#39;s parsing of chunk extensions in HTTP/1.1 messages with chunked encoding can lead to request smuggling issues with some reverse proxies.</p> <p>## Details When encountering a newline character (LF) while parsing a chunk extension, netty interprets the newline as the end of the chunk-size line regardless of whether a preceding carriage return (CR) was found. This is in violation of the HTTP 1.1 standard which specifies that the chunk extension is terminated by a CRLF sequence (see the [RFC](https://datatracker.ietf.org/doc/html/rfc9112#name-chunked-transfer-coding)).</p> <p>This is by itself harmless, but consider an intermediary with a similar parsing flaw: while parsing a chunk extension, the intermediary interprets an LF without a preceding CR as simply part of the chunk extension (this is also in violation of the RFC, because whitespace characters are not allowed in chunk extensions). We can use this discrepancy to construct an HTTP request that the intermediary will interpret as one request but netty will interpret as two (all lines ending with CRLF, notice the LFs in the chunk extension):</p> <p>``` POST /one HTTP/1.1 Host: localhost:8080 Transfer-Encoding: chunked</p> <p>48;\nAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\n0</p> <p>POST /two HTTP/1.1 Host: localhost:8080 Transfer-Encoding: chunked</p> <p>0</p> <p>```</p> <p>The intermediary will interpret this as a single request. Once forwarded to netty, netty will interpret it as two separate requests. This is a…</p> <p><strong>Affected:</strong> Maven: io.netty:netty-codec-http</p> <p>## Summary A flaw in netty&#39;s parsing of chunk extensions in HTTP/1.1 messages with chunked encoding can lead to request smuggling issues with some reverse proxies.</p> <p>## Details When encountering a newline character (LF) while parsing a chunk extension, netty interprets the newline as the end of the chunk-size line regardless of whether a preceding carriage return (CR) was found. This is in violation of the HTTP 1.1 standard which specifies that the chunk extension is terminated by a CRLF sequence (see the [RFC](https://datatracker.ietf.org/doc/html/rfc9112#name-chunked-transfer-coding)).</p> <p>This is by itself harmless, but consider an intermediary with a similar parsing flaw: while parsing a chunk extension, the intermediary interprets an LF without a preceding CR as simply part of the chunk extension (this is also in violation of the RFC, because whitespace characters are not allowed in chunk extensions). We can use this discrepancy to construct an HTTP request that the intermediary will interpret as one request but netty will interpret as two (all lines ending with CRLF, notice the LFs in the chunk extension):</p> <p>``` POST /one HTTP/1.1 Host: localhost:8080 Transfer-Encoding: chunked</p> <p>48;\nAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\n0</p> <p>POST /two HTTP/1.1 Host: localhost:8080 Transfer-Encoding: chunked</p> <p>0</p> <p>```</p> <p>The intermediary will interpret this as a single request. Once forwarded to netty, netty will interpret it as two separate requests. This is a…</p> https://cve.radiocsirt.org/vuln/ghsa-fghv-69vj-qj49 https://cve.radiocsirt.org/vuln/jvndb-2026-020740 <p>Hitachi Infrastructure Analytics Advisor contains the following vulnerability: CVE-2025-48924 Hitachi Ops Center Analyzer contains the following vulnerabilities: CVE-2025-48924 Hitachi Ops Center Analyzer viewpoint contains the following vulnerability: CVE-2025-48924 Hitachi Ops Center Viewpoint contains the following vulnerabilities: CVE-2023-35116, CVE-2025-24970, CVE-2025-25193, CVE-2025-48924, CVE-2025-55163, CVE-2025-58056, CVE-2025-58057</p> <p>Hitachi Infrastructure Analytics Advisor contains the following vulnerability: CVE-2025-48924 Hitachi Ops Center Analyzer contains the following vulnerabilities: CVE-2025-48924 Hitachi Ops Center Analyzer viewpoint contains the following vulnerability: CVE-2025-48924 Hitachi Ops Center Viewpoint contains the following vulnerabilities: CVE-2023-35116, CVE-2025-24970, CVE-2025-25193, CVE-2025-48924, CVE-2025-55163, CVE-2025-58056, CVE-2025-58057</p> https://cve.radiocsirt.org/vuln/jvndb-2026-020740 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15520-1 <p>netty-4.1.126-1.1 on GA media</p> <p>netty-4.1.126-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15520-1 https://cve.radiocsirt.org/vuln/rhsa-2025:17187 <p>netty-codec-http: Netty is vulnerable to request smuggling due to incorrect parsing of chunk extensions netty-codec: netty-codec-compression: Netty&#39;s BrotliDecoder is vulnerable to DoS via zip bomb style attack</p> <p>netty-codec-http: Netty is vulnerable to request smuggling due to incorrect parsing of chunk extensions netty-codec: netty-codec-compression: Netty&#39;s BrotliDecoder is vulnerable to DoS via zip bomb style attack</p> https://cve.radiocsirt.org/vuln/rhsa-2025:17187 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-58056 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: netty, Ubuntu:Pro:16.04:LTS: netty, Ubuntu:16.04:LTS: netty-3.9, Ubuntu:Pro:18.04:LTS: netty, Ubuntu:18.04:LTS: netty-3.9, Ubuntu:Pro:20.04:LTS: netty, Ubuntu:22.04:LTS: netty, Ubuntu:24.04:LTS: netty, Ubuntu:25.10: netty</p> <p>Netty is an asynchronous event-driven network application framework for development of maintainable high performance protocol servers and clients. In versions 4.1.124.Final, and 4.2.0.Alpha3 through 4.2.4.Final, Netty incorrectly accepts standalone newline characters (LF) as a chunk-size line terminator, regardless of a preceding carriage return (CR), instead of requiring CRLF per HTTP/1.1 standards. When combined with reverse proxies that parse LF differently (treating it as part of the chunk extension), attackers can craft requests that the proxy sees as one request but Netty processes as two, enabling request smuggling attacks. This is fixed in versions 4.1.125.Final and 4.2.5.Final.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: netty, Ubuntu:Pro:16.04:LTS: netty, Ubuntu:16.04:LTS: netty-3.9, Ubuntu:Pro:18.04:LTS: netty, Ubuntu:18.04:LTS: netty-3.9, Ubuntu:Pro:20.04:LTS: netty, Ubuntu:22.04:LTS: netty, Ubuntu:24.04:LTS: netty, Ubuntu:25.10: netty</p> <p>Netty is an asynchronous event-driven network application framework for development of maintainable high performance protocol servers and clients. In versions 4.1.124.Final, and 4.2.0.Alpha3 through 4.2.4.Final, Netty incorrectly accepts standalone newline characters (LF) as a chunk-size line terminator, regardless of a preceding carriage return (CR), instead of requiring CRLF per HTTP/1.1 standards. When combined with reverse proxies that parse LF differently (treating it as part of the chunk extension), attackers can craft requests that the proxy sees as one request but Netty processes as two, enabling request smuggling attacks. This is fixed in versions 4.1.125.Final and 4.2.5.Final.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-58056 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2098 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM SPSS ausnutzen, um einen Denial of Service Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM SPSS ausnutzen, um einen Denial of Service Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2098