Netty: Wrapping plain trust manager silently disables hostname verification
Published 15 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected io.netty:netty-handler?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.2.0.Final <4.2.15.Final
- Fixed in
- 4.2.15.Final
mvn versions:use-dep-version -Dincludes=io.netty:netty-handler -DdepVersion=4.2.15.Final -DforceVersion=true- Affected
- <4.1.135.Final
- Fixed in
- 4.1.135.Final
mvn versions:use-dep-version -Dincludes=io.netty:netty-handler -DdepVersion=4.1.135.Final -DforceVersion=trueDetails
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.
Is GHSA-c653-97m9-rcg9 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.netty:netty-handler, and gives you the command that fixes it.
More advisories for io.netty:netty-handler
- CriticalCVE-2026-75595Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext · 8 Sept 2026
- MediumCVE-2026-75596Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing · 8 Sept 2026
- HighCVE-2026-45416Netty: SNI handler pre-allocates up to 16 MiB from nine attacker bytes · 8 Jun 2026
- HighCVE-2026-44249Netty has an IPv6 Subnet Filter Bypass via Incorrect Comparator Masking · 8 Jun 2026
- HighCVE-2025-24970SslHandler doesn't correctly validate packets which can lead to native crash when using native SSLEngine · 10 Feb 2025
- MediumCVE-2023-34462netty-handler SniHandler 16MB allocation · 20 Jun 2023
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.