Back to CVE records
High 7.5Published Aug 22, 2026

CVE-2026-62243Netty 4.2.0 through 4.2.16 TLS Hostname Verification Bypass

Updated under an hour ago ()

Does this affect you?

It affects netty. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness (CWE)
CWE-297
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
VulnCheck
NVD analysis
Awaiting Analysis
Record last updated
Aug 24, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
netty netty
netty:netty (from the name)
from 4.2.0.Final before 4.2.16.Final; 4.2.16.Final not affected
CNA record

References

  • vendor-advisory
  • third-party-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.