Bug 2488437 (CVE-2026-48059) - CVE-2026-48059 netty-codec-haproxy: Netty HAProxy PROXY protocol v2 codec: Denial of Service via memory leak from crafted PROXY protocol headers
Summary: CVE-2026-48059 netty-codec-haproxy: Netty HAProxy PROXY protocol v2 codec: De...
Keywords:
Status: NEW
Alias: CVE-2026-48059
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 16:03 UTC by OSIDB Bzimport
Modified: 2026-08-11 17:43 UTC (History)
103 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:43 UTC
Red Hat Product Errata RHSA-2026:34608 0 None None None 2026-07-02 00:04:25 UTC
Red Hat Product Errata RHSA-2026:37390 0 None None None 2026-07-09 15:29:42 UTC
Red Hat Product Errata RHSA-2026:41951 0 None None None 2026-07-20 11:57:43 UTC
Red Hat Product Errata RHSA-2026:48151 0 None None None 2026-07-29 19:55:20 UTC
Red Hat Product Errata RHSA-2026:50085 0 None None None 2026-08-04 14:00:22 UTC
Red Hat Product Errata RHSA-2026:53644 0 None None None 2026-08-11 16:38:23 UTC
Red Hat Product Errata RHSA-2026:53806 0 None None None 2026-08-11 17:43:10 UTC

Description OSIDB Bzimport 2026-06-12 16:03:02 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, the HAProxy PROXY protocol v2 codec in netty leaks native or heap memory on every connection when a client sends a syntactically valid header containing nested `PP2_TYPE_SSL` TLVs (type-length-value records) at depth two or greater. The leak occurs on the successful parse path — no exception is thrown, the message fires downstream, the decoder removes itself, and the application releases the `HAProxyMessage` normally. Yet the underlying cumulation buffer (a pooled, potentially direct `ByteBuf` allocated by the channel) remains permanently pinned. Versions 4.1.135.Final and 4.2.15.Final patch the issue.
Comment 1 errata-xmlrpc 2026-06-17 23:05:42 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:25 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:36 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:36 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:14 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
Comment 8 errata-xmlrpc 2026-08-04 14:00:16 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 8.1

Via RHSA-2026:50085 https://access.redhat.com/errata/RHSA-2026:50085
Comment 10 errata-xmlrpc 2026-08-11 16:38:17 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7

Via RHSA-2026:53644 https://access.redhat.com/errata/RHSA-2026:53644
Comment 11 errata-xmlrpc 2026-08-11 17:43:04 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 7.4.25

Via RHSA-2026:53806 https://access.redhat.com/errata/RHSA-2026:53806
Note You need to log in before you can comment on or make changes to this bug.