CVE-2026-50010

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,
	SimpleTrustManagerFactory.engineGetTrustManagers() and related paths
	wrap any user-supplied plain X509TrustManager in
	X509TrustManagerWrapper, which extends X509ExtendedTrustManager but
	implements the 3-arg checkServerTrusted(chain, authType, SSLEngine) by
	discarding the SSLEngine and calling the 2-arg delegate. Because the
	object now IS an X509ExtendedTrustManager, neither SunJSSE's internal
	AbstractTrustManagerWrapper nor Netty's own
	OpenSslX509TrustManagerWrapper will re-wrap it to add
	endpoint-identification. Consequently, even though Netty 4.2 sets
	endpointIdentificationAlgorithm="HTTPS" by default, a client built
	with
	`SslContextBuilder.forClient().trustManager(somePlainX509TrustManager)`
	performs no hostname verification at all. Versions 4.1.135.Final and
	4.2.15.Final patch the issue.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-50010</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-50010</url>
    </references>
    <dates>
      <discovery>2026-06-12</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>