https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T04:31:55.546675+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-09804 bdu:2026-09804 2026-10-03T04:31:56.249407+00:00 bdu:2026-09804 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0773 certfr-2026-avi-0773 — De multiples vulnérabilités ont été découvertes dans les produits Atlassian. Certaines d'entre elles permettent à un at… 2026-10-03T04:31:56.249474+00:00 certfr-2026-avi-0773 https://cve.radiocsirt.org/vuln/cleanstart-2026-bk55944 Withdrawn: CLEANSTART-2026-BK55944 — Security fixes for CVE-2025-59250, CVE-2026-0636, CVE-2026-33870, CVE-2026-33871, CVE-2026-39852, CVE-2026-41417, CVE-2… 2026-10-03T04:31:56.249496+00:00

Withdrawn by the publisher.

Affected: CleanStart: keycloak

Multiple security vulnerabilities affect the keycloak package. These issues are resolved in later releases. See references for individual vulnerability details.

 https://cve.radiocsirt.org/vuln/euvd-2026-371768 EUVD-2026-371768 2026-10-03T04:31:56.249533+00:00 EUVD-2026-371768 https://cve.radiocsirt.org/vuln/fkie_cve-2026-42584 fkie_cve-2026-42584 2026-10-03T04:31:56.249546+00:00

Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpClientCodec pairs each inbound response with an outbound request by queue.poll() once per response, including for 1xx. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message’s body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.

 https://cve.radiocsirt.org/vuln/ghsa-57rv-r2g8-2cj3 GHSA-57rv-r2g8-2cj3 — Netty has HttpClientCodec response desynchronization 2026-10-03T04:31:56.249575+00:00

Affected: Maven: io.netty:netty-codec-http

### Summary If HttpClientCodec is configured, there are use cases when a response body from one request, can be parsed as another's.

### Details HttpClientCodec pairs each inbound response with an outbound request by `queue.poll()` once per response, including for `1xx`. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message’s body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset.

Prerequisites - HTTP/1.1 pipelining - HEAD in the pipeline - The server sends 1xx

### PoC

```java @Test public void test() { EmbeddedChannel channel = new EmbeddedChannel(new HttpClientCodec());

assertTrue(channel.writeOutbound(new DefaultFullHttpRequest(HttpVersion.HTTP_1_1, HttpMethod.GET, "/1"))); ByteBuf request = channel.readOutbound(); request.release(); assertNull(channel.readOutbound());

assertTrue(channel.writeOutbound(new DefaultFullHttpRequest(HttpVersion.HTTP_1_1, HttpMethod.HEAD, "/2"))); request = channel.readOutbound(); request.release(); assertNull(channel.readOutbound());

String responseStr = "HTTP/1.1 103 Early Hints\r\n\r\n" + "HTTP/1.1 200 OK\r\nContent-Length: 5\r\n\r\nhello" + "HTTP/1.1 200 OK\r\n\r\n"; assertTrue(channel.writeInbound(Unpooled.copiedBuffer(r…

 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10795-1 openSUSE-SU-2026:10795-1 — netty-4.1.133-1.1 on GA media 2026-10-03T04:31:56.249625+00:00

netty-4.1.133-1.1 on GA media

 https://cve.radiocsirt.org/vuln/rhsa-2026:23808 RHSA-2026:23808 — Red Hat Security Advisory: Red Hat build of Quarkus 3.27.4 release and security update 2026-10-03T04:31:56.249650+00:00

netty: io.netty/netty-handler-proxy: Netty: HTTP Header Injection via HttpProxyHandler Disabled Validation netty: Netty: High integrity impact due to improper DNS domain name constraint enforcement netty: io.netty/netty-codec-http: Netty: HTTP Request Smuggling due to improper handling of conflicting HTTP/1.0 headers netty: io.netty/netty-codec-http: Netty: Incorrect HTTP response parsing leads to data confusion netty: io.netty/netty-codec-http: io.netty/netty-codec-http2: Netty: Denial of Service via unbounded memory allocation in HTTP content decompression

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-42584 UBUNTU-CVE-2026-42584 2026-10-03T04:31:56.249674+00:00

Affected: Ubuntu:Pro:14.04:LTS: netty, Ubuntu:Pro:16.04:LTS: netty, Ubuntu:Pro:18.04:LTS: netty, Ubuntu:Pro:20.04:LTS: netty, Ubuntu:Pro:22.04:LTS: netty, Ubuntu:Pro:24.04:LTS: netty, Ubuntu:25.10: netty, Ubuntu:Pro:26.04:LTS: netty

Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpClientCodec pairs each inbound response with an outbound request by queue.poll() once per response, including for 1xx. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message’s body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1372 WID-SEC-W-2026-1372 — Netty: Mehrere Schwachstellen 2026-10-03T04:31:56.249710+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Netty ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.