GHSA-c653-97m9-rcg9

Netty: Wrapping plain trust manager silently disables hostname verification

At a glance

Published
Updated
CVE
CVE-2026-50010
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Description

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.

Affected packages

PackageVersions
Maven · io.netty:netty-handlerintroduced 4.2.0.Final, fixed 4.2.15.Final
Maven · io.netty:netty-handlerintroduced 0, fixed 4.1.135.Final

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database