CVE-2026-62243
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.7
- CVSS vector
- 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
- EPSS probability
- 0.15%
- CWE
- CWE-297
- Published
- 2026-08-22
- Last modified
- 2026-08-24
Affected products
- netty netty
- netty netty
- netty netty
- netty netty
Weakness type
Related vulnerabilities
- CVE-2026-79636 — Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to...
- CVE-2026-84197 — In Eclipse Ditto's Node.js JavaScript client, all released versions of...
- CVE-2026-84393 — A improper validation of certificate with host mismatch vulnerability in Fortinet FortiOS 7.6.1...
- CVE-2026-79943 — Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to...
- CVE-2026-9744 — Vulnerabilities exists in IBM Netezza Software
- CVE-2026-53583 — libgit2: Inverted IP SubjectAltName Comparison in OpenSSL Backend
- CVE-2026-49457 — QUIC has Broken TLS verification
- CVE-2026-65942 — Apache Ranger: Clients accept TLS certificates issued for other hostnames