~ / search / GHSA-h2qv-fj59-j46j

GHSA-h2qv-fj59-j46j

Netty HAProxy: Unbalanced Reference Count in Nested PP2_TYPE_SSL TLV Parsing Leads to Memory Exhaustion

Source: GitHub Advisory Database (reviewed) High CVE-2026-48059

Packages

EcosystemPackageAffectedFixed in
Maven io.netty:netty-codec-haproxy >= 4.2.0.Final, < 4.2.15.Final 4.2.15.Final
Maven io.netty:netty-codec-haproxy < 4.1.135.Final 4.1.135.Final

Details

As written in the advisory (Markdown source, shown as plain text).

### Impact 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.

References

External links from the advisory. They lead to third-party sites.