CVE-2026-100665
highNetty 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 pla…
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/netty/netty/commit/09e72c4fd8007277121ed48db63a124b112b96fe disclosure@vulncheck.com
- https://github.com/netty/netty/commit/994e887ed9 disclosure@vulncheck.com
- https://github.com/netty/netty/security/advisories/GHSA-mj35-3qqm-q387 disclosure@vulncheck.com
- https://www.vulncheck.com/advisories/netty-4.2.11-through-4.2.17-quic-hostname-verificatio... disclosure@vulncheck.com
- https://github.com/netty/netty/security/advisories/GHSA-mj35-3qqm-q387 134c704f-9b21-4f2e-91b3-4a467353bcc0