CVE-2026-42584 is a vulnerability in Netty's HttpClientCodec where certain sequences of HTTP responses cause incorrect pairing of responses to requests. This leads to subsequent HTTP responses being parsed from incorrect offsets, potentially causing information disclosure or data integrity issues. The flaw is fixed in Netty versions 4.2.13.Final and 4.1.133.Final.
CVE-2026-42583 is a high-severity vulnerability in the Netty network application framework affecting versions prior to 4.2.13.Final and 4.1.133.Final. The flaw involves uncontrolled resource consumption due to the Lz4FrameDecoder allocating large ByteBuf buffers (up to 32 MB) based on decompressedLength before decompression. An attacker can trigger this allocation with minimal input, potentially causing denial of service by exhausting memory resources. The issue is fixed in Netty versions 4.2.13.Final and 4.1.133.Final.
CVE-2026-42580 is a medium severity vulnerability in Netty, an asynchronous network application framework. The issue involves an integer overflow in the chunk size parser prior to versions 4.2.13.Final and 4.1.133.Final, which enables HTTP request/response smuggling attacks. This vulnerability has been fixed in the specified versions.
Netty versions prior to 4.2.13.Final and 4.1.133.Final contain a vulnerability in their DNS codec where domain name constraints defined by RFC 1035 are not properly enforced during encoding and decoding. This flaw allows remote attackers to exploit the decoder with malicious DNS responses or the encoder with user-influenced hostnames, resulting in a high integrity impact. The issue is fixed in versions 4.2.13.Final and 4.1.133.Final.
Netty versions from 4.2.0.Final up to but not including 4.2.13.Final contain a vulnerability in the epoll transport where TCP connections that receive a RST after being half-closed are not properly detected and closed. This results in stale channels that remain open indefinitely and can cause a 100% CPU busy-loop in the event loop thread. The issue is fixed in version 4.2.13.Final.
CVE-2026-42578 is a vulnerability in Netty's HttpProxyHandler component where HTTP CONNECT requests are constructed with header validation disabled. This allows an attacker who can influence outbound headers to inject arbitrary HTTP headers into the CONNECT request sent to a proxy server. The issue is fixed in Netty versions 4.2.13.Final and 4.1.133.Final.
CVE-2026-42581 is a vulnerability in Netty's HttpObjectDecoder affecting versions prior to 4.2.13.Final and 4.1.133.Final. It occurs because Netty does not properly strip a conflicting Content-Length header in HTTP/1.0 requests that also include Transfer-Encoding: chunked. This allows an attacker to craft HTTP/1.0 requests that cause downstream proxies or handlers to misinterpret message boundaries, enabling HTTP request smuggling attacks. The issue is fixed in versions 4.2.13.Final and 4.1.133.Final.
Netty versions up to 4.2.12.Final and 4.1.132.Final contain a CRLF injection vulnerability due to insufficient validation in the setUri() method of DefaultHttpRequest and DefaultFullHttpRequest. This allows an attacker to inject CRLF characters into the HTTP or RTSP request line, potentially enabling HTTP request smuggling, desynchronization, or RTSP request injection. The issue is fixed in versions 4.2.13.Final and 4.1.133.Final.
Netty versions prior to 4.1.124.Final and 4.2.4.Final are affected by a vulnerability in the HTTP/2 protocol handling that allows attackers to bypass the maximum concurrent streams limit. This leads to resource exhaustion and a potential distributed denial of service (DDoS) condition. The issue is identified as CWE-770, involving allocation of resources without proper limits or throttling. The vulnerability has been patched in versions 4.1.124.Final and 4.2.4.Final.