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
Affects nettySource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 4.2.17 : patch netty soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.2.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro 14.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-infra-legacy/trustyOther threats | Affected
| Fixed in– |
Ubuntu Pro 16.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps-legacy/xenialOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 24.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Netty versions 4.2.17.Final and 4.1.137.Final. Users should upgrade to these or later versions to ensure hostname verification is properly enforced on the OpenSSL client path. No other mitigation steps are indicated by the vendor advisory.
Description
Netty versions from 4.2.0.Final through 4.2.16.Final and up to 4.1.136.Final disable TLS hostname verification on the OpenSSL client path when using a plain X509TrustManager and Unsafe-based trust-manager wrapping is unavailable (Java 25+). This allows a man-in-the-middle attacker to present a certificate for a different hostname that is accepted without validation. The issue is fixed in versions 4.2.17.Final and 4.1.137.Final.
References
- github.com/netty/netty/security/advisories/GHSA-p85m-gvr3-788c (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-62243 (opens in a new tab)
- vulncheck.com/advisories/netty-through-tls-hostname-verification-bypass (opens in a new tab)
- ubuntu.com/security/CVE-2026-62243 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-62243 (opens in a new tab)