{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-48059: Netty HAProxy: Unbalanced Reference Count in Nested PP2_TYPE_SSL TLV Parsing Leads to Memory Exhaustion","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-48059","status":"final","version":"1","initial_release_date":"2026-06-12T14:42:44.677Z","current_release_date":"2026-06-12T16:19:45.689Z","revision_history":[{"date":"2026-06-12T14:42:44.677Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"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.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-48059 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-48059"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-48059"},{"category":"external","summary":"https://github.com/netty/netty/security/advisories/GHSA-h2qv-fj59-j46j","url":"https://github.com/netty/netty/security/advisories/GHSA-h2qv-fj59-j46j"},{"category":"external","summary":"https://github.com/netty/netty/releases/tag/netty-4.1.135.Final","url":"https://github.com/netty/netty/releases/tag/netty-4.1.135.Final"},{"category":"external","summary":"https://github.com/netty/netty/releases/tag/netty-4.2.15.Final","url":"https://github.com/netty/netty/releases/tag/netty-4.2.15.Final"}]},"product_tree":{"branches":[{"category":"vendor","name":"netty","branches":[{"category":"product_name","name":"netty","branches":[{"category":"product_version","name":">= 4.2.0.Final, < 4.2.15.Final","product":{"name":"netty netty >= 4.2.0.Final, < 4.2.15.Final","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":"< 4.1.135.Final","product":{"name":"netty netty < 4.1.135.Final","product_id":"CSAFPID-2","product_identification_helper":{"cpe":"cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-48059","title":"Netty HAProxy: Unbalanced Reference Count in Nested PP2_TYPE_SSL TLV Parsing Leads to Memory Exhaustion","notes":[{"category":"description","text":"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.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1","CSAFPID-2"]},"scores":[{"cvss_v4":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","baseScore":8.7,"baseSeverity":"HIGH"},"products":["CSAFPID-1","CSAFPID-2"]}],"remediations":[{"category":"none_available","details":"No fixed version is published yet. Monitor the upstream advisory.","product_ids":["CSAFPID-1","CSAFPID-2"]}]}]}