A resource release issue exists in netty-incubator-codec-ohttp versions from 0.0.20.Final up to but not including 0.0.27.Final. The OHttpClientCodec and OHttpServerCodec components retain the outer cumulation buffer after an OHTTP exchange completes, causing memory to be held unnecessarily during long-lived idle keep-alive connections. This can lead to increased memory usage and availability pressure. The issue is fixed in version 0.0.27.Final.
CVE-2026-63202 is a high-severity vulnerability in netty-incubator-codec-ohttp prior to version 0.0.23.Final. It involves uncontrolled resource consumption due to improper handling of corrupted or truncated Binary HTTP field lines during parsing. An unauthenticated attacker can exploit this to cause a Netty event-loop thread to consume full CPU indefinitely, leading to denial of service by exhausting event-loop resources. The issue is fixed in version 0.0.23.Final.
CVE-2026-61827 is a high-severity vulnerability in netty-incubator-codec-ohttp prior to version 0.0.23.Final. The BinaryHttpParser component does not enforce limits on encoded variable-length fields controlled by a remote peer, allowing an attacker to cause the decoder to buffer data indefinitely. This can exhaust memory resources and result in a denial of service. The issue is fixed in version 0.0.23.Final.
CVE-2026-63124 is a high-severity vulnerability in netty-incubator-codec-ohttp prior to version 0.0.23.Final. The issue arises from the BinaryHttpParser.readFieldLine method incorrectly treating a complete field line ending exactly at a known field-section boundary as incomplete, causing the parser to spin indefinitely. This leads to uncontrolled resource consumption, potentially pinning the Netty event-loop or worker thread. The vulnerability is fixed in version 0.0.23.Final.
CVE-2026-61798 is a high-severity vulnerability in netty-incubator-codec-ohttp prior to version 0.0.23.Final. The issue involves sensitive HPKE private key material being exposed in logs or telemetry due to insecure toString implementations and exception messages. This exposure can allow unauthorized actors who access logs to recover private keys, potentially compromising the confidentiality and authenticity of Oblivious HTTP messages. The vulnerability is fixed in version 0.0.23.Final.
CVE-2026-61799 is an integer overflow vulnerability in netty-incubator-codec-ohttp versions prior to 0.0.23.Final. The flaw occurs in the BinaryHttpParser component, where attacker-controlled variable-length integers can cause integer wraparound in offset calculations. This can lead to unchecked bounds exceptions, causing the affected service to fail or close the channel repeatedly, resulting in a denial of service. The issue does not lead to memory corruption or information disclosure. The vulnerability is fixed in version 0.0.23.Final.
CVE-2026-116542 is a vulnerability in netty-tcnative before version 2.0.84.Final where improper handling of Unicode encoding in JNI NewStringUTF decoding allows remote unauthenticated clients to spoof SNI hostnames. Attackers can use overlong encodings in the ClientHello server_name field to confuse SNI-based certificate selection, access decisions, and logging.
CVE-2026-116541 is a denial of service vulnerability in netty-tcnative versions before 2.0.84.Final. It arises from an incorrect calculation in the tcn_write_to_bytebuffer BIO write callback, which overreports bytes consumed. Remote TLS 1.3 peers can exploit this to cause truncated flights, connection failures, or JVM process aborts during post-handshake records such as NewSessionTicket or KeyUpdate.
A use-after-free vulnerability exists in netty-tcnative versions 2.0.66.Final through before 2.0.84.Final when built against OpenSSL 3.x. The flaw occurs during TLS session ticket key rotation, where OpenSSL may read freed HMAC keys, potentially causing crashes or corruption in ticket processing.
Netty netty-tcnative before 2.0.84.Final contains a heap buffer overflow vulnerability in the tcn_write_to_bytebuffer BIO callback caused by failing to wrap the non-application ring buffer write index. Remote TLS peers can drive handshake, renegotiation, or post-handshake messages into this buffer, triggering an out-of-bounds memcpy that crashes the JVM process.
netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, the OHTTP gateway decryption path in codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpRequestResponseContext.java allocates a pooled direct ByteBuf for decrypted plaintext before the AEAD tag is verified. When an invalid tag causes decryptChunk() to throw CryptoException, OHttpRequestResponseContext.decodeChunk() does not release the ByteBuf because the allocation is not guarded by try/finally. Repeated invalid encrypted requests can therefore leak native off-heap memory until the gateway is unable to continue serving requests. This issue is fixed in version 0.0.23.Final.
CVE-2026-75595 is a critical vulnerability in the Netty network application framework affecting versions prior to 4.1.137.Final and 4.2.17.Final. The flaw arises from an improper check of the TLS handshake header offset in SslClientHelloHandler#decode, which can cause an IndexOutOfBoundsException and lead to the selection of a default SSL context instead of the intended SNI-specific context. This behavior allows an unauthenticated remote attacker to bypass mutual TLS authentication requirements in certain deployment configurations where client authentication is enforced solely by per-SNI settings. The issue is fixed in Netty versions 4.1.137.Final and 4.2.17.Final.
CVE-2026-75596 is a high-severity vulnerability in the Netty framework affecting versions prior to 4.1.137.Final and between 4.2.0.Final and before 4.2.17.Final. It involves inefficient algorithmic complexity in the TLS handshake processing, where an unauthenticated remote peer can cause excessive CPU usage by sending a large ClientHello message fragmented into many small TLS records. This results in quadratic CPU workload on the event loop, degrading TLS handling performance for other clients. The issue is fixed in Netty versions 4.1.137.Final and 4.2.17.Final.
The netty incubator codec.bhttp is a java language binary http parser. Prior to version 0.0.22.FInal, the codec-ohttp implementation of draft-ietf-ohai-chunked-ohttp does not verify that a cryptographically-signed final chunk was received before the outer HTTP body terminates. An on-path adversary (the OHTTP relay itself, or any MITM on the relay↔gateway or relay↔client transport) can forward a prefix of a legitimate chunked-OHTTP message—cut at a non-final chunk boundary—and close the outer body cleanly, producing no decryption error and no exception in the receiving application. Version 0.0.22.Final fixes the issue.
The netty incubator codec.bhttp is a java language binary http parser. The library implements Oblivious HTTP (RFC 9458) using BoringSSL's HPKE C library via JNI. When deriving native memory addresses for cryptographic operations versions prior to 0.0.22.Final provide a fallback path for direct ByteBufs that do not expose their memory address through `hasMemoryAddress()`. This fallback occurs when `sun.misc.Unsafe` is unavailable to Netty — for example, when the JVM is started with `-Dio.netty.noUnsafe=true`, when a SecurityManager restricts Unsafe access, or when running on non-HotSpot JVMs. In these configurations, Netty's default `PooledByteBufAllocator` returns `PooledDirectByteBuf` instances for which `hasMemoryAddress()` returns false. Under the enabling JVM configuration, an unauthenticated network attacker can cause the OHTTP gateway to corrupt memory belonging to other concurrent connections and disclose the contents of adjacent pooled direct buffers by triggering cryptographic operations with crafted OHTTP requests. The corruption occurs regardless of whether the AEAD tag verification succeeds, as BoringSSL zeroizes the output buffer on failure. The information disclosure path provides the attacker with the encryption key needed to extract the leaked data. This violates the confidentiality and integrity of all connections sharing the same Netty buffer arena. Version 0.0.22.Final fixes the issue.
The netty incubator codec.bhttp is a java language binary http parser. Prior to version 0.0.21.Final, HKDF_expand returns non-NULL on failure. The byte[] is filled with zeros and has no way to distinguish success from failure. Since this output is used as HKDF key material for the response AEAD, a failure silently produces an all-zero key. When EVP_HPKE_CTX_export fails it also returns an empty byte[] array filled with zeros. This byte[] feeds directly into OHttpCrypto.createResponseAEAD(...). A silent all-zero export secret would produce a deterministic, attacker-predictable AEAD key. Version 0.0.21.Final patches the issue.
CVE-2026-44248 is a denial of service vulnerability in Netty's MQTT 5 decoder where the Properties section of the MQTT header is parsed and buffered without applying message size limits. This causes excessive CPU and memory consumption due to repeated parsing and buffering until completion. The issue affects Netty versions prior to 4.2.13.Final and 4.1.133.Final and is fixed in those versions.
Netty versions prior to 4.2.13.Final and 4.1.133.Final contain a vulnerability in HTTP content decompression where the maxAllocation limit is ignored for Brotli (br), Zstandard (zstd), and Snappy content encodings. This allows an attacker to send specially crafted compressed payloads that cause unbounded memory allocation, leading to an out-of-memory denial of service. The issue affects both HTTP/1.x and HTTP/2 decompression components. The vulnerability is fixed in versions 4.2.13.Final and 4.1.133.Final.
Netty versions prior to 4.2.13.Final and 4.1.133.Final contain a CRLF injection vulnerability in the RedisEncoder component. This occurs because user-controlled string content is written directly to the network output buffer without sanitizing CRLF characters. Since the Redis Serialization Protocol uses CRLF as delimiters, an attacker controlling Redis message content can inject arbitrary commands or forge responses. The vulnerability is fixed in versions 4.2.13.Final and 4.1.133.Final.
Netty versions prior to 4.2.13.Final and 4.1.133.Final contain a vulnerability where malformed Transfer-Encoding headers are incorrectly parsed, allowing HTTP request/response smuggling attacks. This flaw has been addressed in versions 4.2.13.Final and 4.1.133.Final.