Kurz gesagt
- CVE-2026-45416 ist eine Schwachstelle (HOCH (CVSS 7.5)) in io.netty:netty-handler, netty (netty).
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.92%, höher als bei 60.3% aller Schwachstellen.
- Abhilfe: auf 4.2.15.Final, 4.1.135.Final, 4.2.15, 4.1.135 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| io.netty:netty-handler Maven | ≥ 4.2.0.Final, < 4.2.15.Final< 4.1.135.Final
| 4.2.15.Final4.1.135.Final
|
| netty | ≥ 4.2.0, < 4.2.15< 4.1.135
| 4.2.154.1.135
|
Description
SslClientHelloHandler.decode() reads the 24-bit TLS handshake length and, when the ClientHello does not fit in the first record, eagerly allocates ctx.alloc().buffer(handshakeLength) (line 161). The guard at line 140 is handshakeLength > maxClientHelloLength && maxClientHelloLength != 0, and the commonly-used SniHandler/AbstractSniHandler constructors (SniHandler(Mapping), SniHandler(AsyncMapping), AbstractSniHandler()) pass maxClientHelloLength=0 and handshakeTimeoutMillis=0, so the length guard is disabled and no timeout is scheduled. A 16 MiB request exceeds the default pooled chunk size and becomes a huge/unpooled allocation performed immediately. The buffer is retained in the handler until the channel closes.
NVD description
Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, SslClientHelloHandler.decode() reads the 24-bit TLS handshake length and, when the ClientHello does not fit in the first record, eagerly allocates `ctx.alloc().buffer(handshakeLength)` (line 161). The guard at line 140 is `handshakeLength > maxClientHelloLength && maxClientHelloLength != 0`, and the commonly-used SniHandler/AbstractSniHandler constructors (SniHandler(Mapping), SniHandler(AsyncMapping), AbstractSniHandler()) pass maxClientHelloLength=0 and handshakeTimeoutMillis=0, so the length guard is disabled and no timeout is scheduled. A 16 MiB request exceeds the default pooled chunk size and becomes a huge/unpooled allocation performed immediately. The buffer is retained in the handler until the channel closes. Versions 4.1.135.Final and 4.2.15.Final patch the issue.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free