CVE-2026-62243
8.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Summary
Netty (io.netty:netty-handler) versions from 4.2.0.Final through 4.2.16.Final and versions through 4.1.136.Final disable TLS hostname verification on the SslProvider.OPENSSL client path when a plain (non-extended) X509TrustManager is used and Unsafe-based trust-manager wrapping is unavailable (Java 25+). In this configuration the OpenSSL client does not perform hostname verification, allowing a man-in-the-middle attacker to present a certificate issued for a different hostname that is accepted without validation. Fixed in 4.2.17.Final and 4.1.137.Final.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| netty | netty | 4.2.0.Final < 4.2.16.Final | affected |
| netty | netty | 4.2.16.Final | unaffected |
| netty | netty | 0 < 4.1.137.Final | affected |
| netty | netty | 4.1.137.Final | unaffected |
Weaknesses
- CWE-297: Improper Validation of Certificate with Host Mismatch
References
- https://github.com/netty/netty/security/advisories/GHSA-p85m-gvr3-788c
- https://www.vulncheck.com/advisories/netty-through-tls-hostname-verification-bypass
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.