Answer in brief
CVE-2026-48059 records a High severity (CVSS 7.5) vulnerability in Netty HAProxy: Unbalanced Reference Count in Nested PP2_TYPE_SSL TLV Parsing Leads to Memory Exhaustion. The current sources do not mark it as known exploited. The current feed maps netty/netty (generic), io.netty:netty-codec-haproxy (maven), io.netty:netty-codec-haproxy (maven), io.netty:netty-codec-haproxy (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps netty/netty (generic), io.netty:netty-codec-haproxy (maven), io.netty:netty-codec-haproxy (maven), io.netty:netty-codec-haproxy (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| netty/nettygeneric | >= 4.2.0.Final, < 4.2.15.Final || < 4.1.135.Final | Not reported |
| io.netty:netty-codec-haproxymaven | >=4.2.0.Final,<=4.2.14.Final | 4.2.15.Final |
| io.netty:netty-codec-haproxymaven | <=4.1.134.Final | 4.1.135.Final |
| io.netty:netty-codec-haproxymaven | >=4.2.0.Final <4.2.15.Final | 4.2.15.Final |
| io.netty:netty-codec-haproxymaven | >=0 <4.1.135.Final | 4.1.135.Final |
Published upstream
Jun 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.