CVE-2026-100665
Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypass
- State
- Published
- Severity
- 8.7 High
- Published
- Sep 26, 2026
- Updated
- Oct 2, 2026
- Reserved
- Sep 26, 2026
Description
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 8.7 High | 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 | VulnCheck |
| 3.1 | 7.5 High | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | VulnCheck |
Weaknesses
- CWE-295 Improper Certificate Validation
Affected Products
| Product | Versions |
|---|---|
nettynetty |
|
References
- GitHub Security Advisory (GHSA-mj35-3qqm-q387)vendor-advisory
- Patch Commitpatch
- Patch Commitpatch
- VulnCheck Advisory: Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypassthird-party-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.