CVE-2026-100665Netty 4.2.11 through 4.2.17 QUIC 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.
EPSS puts the chance of exploitation in the next 30 days at 0.29%, higher than 20% of scored CVEs.
Do this next
Free account, 1 product
Netty versions from 4.2.11.Final before 4.2.18.Final contain an incomplete hostname verification fix in the QUIC certificate verification path when using a plain X509TrustManager. The BoringSSLCertificateVerifyCallback discards the SSLEngine for plain trust managers, preventing endpoint identification from running even when HTTPS verification is configured. Attackers on the network path can present a certificate chain for the wrong hostname that the plain trust manager accepts, bypassing hostname authentication for QUIC clients.
- 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-295
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.29% (percentile 20)
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Oct 2, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
netty netty netty:netty (from the name) | from 4.2.11.Final before 4.2.18.Final; 4.2.18.Final not affected | CNA record |
References
- https://github.com/netty/netty/security/advisories/GHSA-mj35-3qqm-q387vendor-advisory
- https://github.com/netty/netty/commit/09e72c4fd8007277121ed48db63a124b112b96fepatch
- https://github.com/netty/netty/commit/994e887ed9patch
- https://www.vulncheck.com/advisories/netty-4.2.11-through-4.2.17-quic-hostname-verification-bypassthird-party-advisory
The CVE record on cve.org NVD's entry
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.