CVE-2026-50010
Netty is a network application framework for development of …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/netty/netty/releases/tag/netty-4.1.135.Final
- github.com/netty/netty/releases/tag/netty-4.2.15.Final
- github.com/netty/netty/security/advisories/GHSA-c653-97m9-rcg9
- nvd.nist.gov/vuln/detail/CVE-2026-50010
- github.com/advisories/GHSA-c653-97m9-rcg9
- access.redhat.com/errata/RHSA-2026:26017
- access.redhat.com/errata/RHSA-2026:26018
- access.redhat.com/errata/RHSA-2026:26586
- nvd.nist.gov/vuln/detail/CVE-2026-50010
- cve.org/CVERecord?id=CVE-2026-50010
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.