{"id":"CVE-2026-100665","published":"2026-09-26T14:16:49.677","lastModified":"2026-09-28T15:23:38.510","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.","cvssScore":7.5,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","cwes":["CWE-295"],"vendors":[],"products":[],"references":[{"url":"https://github.com/netty/netty/commit/09e72c4fd8007277121ed48db63a124b112b96fe","tags":[]},{"url":"https://github.com/netty/netty/commit/994e887ed9","tags":[]},{"url":"https://github.com/netty/netty/security/advisories/GHSA-mj35-3qqm-q387","tags":[]},{"url":"https://www.vulncheck.com/advisories/netty-4.2.11-through-4.2.17-quic-hostname-verification-bypass","tags":[]}],"exploitRefs":[{"url":"https://github.com/netty/netty/commit/09e72c4fd8007277121ed48db63a124b112b96fe","tags":[]},{"url":"https://github.com/netty/netty/commit/994e887ed9","tags":[]},{"url":"https://github.com/netty/netty/security/advisories/GHSA-mj35-3qqm-q387","tags":[]}],"hasPoc":true,"ai":null}