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.
References
Configurations
No configuration.
History
02 Oct 2026, 16:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/netty/netty/security/advisories/GHSA-mj35-3qqm-q387 - |
26 Sep 2026, 14:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-26 14:16
Updated : 2026-10-02 16:16
NVD link : CVE-2026-100665
Mitre link : CVE-2026-100665
CVE.ORG link : CVE-2026-100665
JSON object : View
Products Affected
No product.
CWE
CWE-295
Improper Certificate Validation
