Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypass
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.
CVE-2026-100665
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-100665
netty
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "netty",
"product": "netty",
"versions": [
{
"status": "affected",
"version": "4.2.11.Final",
"lessThan": "4.2.18.Final",
"versionType": "custom"
},
{
"status": "unaffected",
"version": "4.2.18.Final",
"versionType": "custom"
}
],
"packageURL": "pkg:maven/io.netty/netty-codec-classes-quic",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-100665
Source reference:
/cveMetadata/cveId
Publisher severity
high
Source reference: /containers/cna/metrics
- Event
- #8000 · Revision 1
- Added to Heist Feed
- Publisher date