Bug 2488391 (CVE-2026-45416) - CVE-2026-45416 netty-handler: Netty: Denial of Service due to eager buffer allocation in TLS handshake
Summary: CVE-2026-45416 netty-handler: Netty: Denial of Service due to eager buffer al...
Keywords:
Status: NEW
Alias: CVE-2026-45416
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-12 15:02 UTC by OSIDB Bzimport
Modified: 2026-07-29 19:55 UTC (History)
109 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:26586 0 None None None 2026-06-17 23:05:38 UTC
Red Hat Product Errata RHSA-2026:34608 0 None None None 2026-07-02 00:04:29 UTC
Red Hat Product Errata RHSA-2026:37390 0 None None None 2026-07-09 15:30:01 UTC
Red Hat Product Errata RHSA-2026:41951 0 None None None 2026-07-20 11:57:59 UTC
Red Hat Product Errata RHSA-2026:48151 0 None None None 2026-07-29 19:55:06 UTC

Description OSIDB Bzimport 2026-06-12 15:02:08 UTC
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.

Comment 1 errata-xmlrpc 2026-06-17 23:05:38 UTC
This issue has been addressed in the following products:

  Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.2.SP1

Via RHSA-2026:26586 https://access.redhat.com/errata/RHSA-2026:26586

Comment 2 errata-xmlrpc 2026-07-02 00:04:29 UTC
This issue has been addressed in the following products:

  Streams for Apache Kafka 2.9.4

Via RHSA-2026:34608 https://access.redhat.com/errata/RHSA-2026:34608

Comment 5 errata-xmlrpc 2026-07-09 15:29:56 UTC
This issue has been addressed in the following products:

  Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16

Via RHSA-2026:37390 https://access.redhat.com/errata/RHSA-2026:37390

Comment 6 errata-xmlrpc 2026-07-20 11:57:54 UTC
This issue has been addressed in the following products:

  Red Hat Data Grid 8.6.2

Via RHSA-2026:41951 https://access.redhat.com/errata/RHSA-2026:41951

Comment 7 errata-xmlrpc 2026-07-29 19:55:00 UTC
This issue has been addressed in the following products:

  Cryostat 4 on RHEL 9

Via RHSA-2026:48151 https://access.redhat.com/errata/RHSA-2026:48151


Note You need to log in before you can comment on or make changes to this bug.