CVE-2026-62243

Published: Ago 22, 2026 Last Modified: Ago 22, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,7
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
HIGH 7,5
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: none
Availability: none

Description

AI Translation Available

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.

297

Improper Validation of Certificate with Host Mismatch

Incomplete
Common Consequences
Security Scopes Affected:
Access Control Authentication Other
Potential Impacts:
Gain Privileges Or Assume Identity Other
Applicable Platforms
Technologies: Not Technology-Specific, Mobile, Web Based
View CWE Details
https://github.com/netty/netty/security/advisories/GHSA-p85m-gvr3-788c
https://www.vulncheck.com/advisories/netty-through-tls-hostname-verification-by…