CVE and update status of the FreeBSD ports tree4,826 unaddressed CVEs in 618 portsAll times are CET

CVE details

CVE-2026-48059

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.

Score
8.7 high
Published
2026-06-12
Links
NVD · cve.org

Affected ports (1)

PortPackageVersionStatusMaintainer
java/nettynetty4.1.53_2unaddressedglewis@FreeBSD.org

Template for a VuXML entry

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>netty</name>
	<range><lt>4.1.135</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-48059</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-48059</url>
    </references>
    <dates>
      <discovery>2026-06-12</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>