CVE-2026-100665

Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypass

Published Sep 26, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Netty 4.2.11.Final to 4.2.17.Final contain an incomplete hostname verification routine in the QUIC certificate path when a plain X509TrustManager is used. The callback discards the SSLEngine required for endpoint identification, causing the hostname check to be skipped even when HTTPS verification is configured. This flaw allows an attacker to supply a certificate chain for an unintended hostname that the plain trust manager accepts, resulting in a man‑in‑the‑middle attack that bypasses authentication and can expose confidential data or impersonate the server.

Affected Systems

Any application that incorporates Netty versions 4.2.11.Final through 4.2.17.Final and utilizes the QUIC protocol with a vanilla X509TrustManager is affected. Projects that depend on these Netty releases for client or server QUIC communication must verify their version and configuration.

Risk and Exploitability

The likely attack vector is an attacker on the network path manipulating the TLS handshake to present a forged certificate chain for the wrong hostname. The vulnerability operates purely on the network layer and does not require local privileges, enabling a remote attacker who can observe or modify traffic to the QUIC endpoint to bypass hostname authentication. The CVSS score is 8.7, EPSS data are unavailable, and the vulnerability is not listed in CISA's KEV catalog.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Netty to version 4.2.18.Final or later where the hostname verification logic has been corrected.
  • If upgrading is not immediately possible, replace the plain X509TrustManager with a trusted manager that performs proper endpoint identification or apply a custom TrustManager that enforces hostname checks for QUIC connections.
  • As a temporary shield, restrict QUIC traffic to highly trusted networks or disable QUIC endpoints until the patch or configuration change can be deployed.

Generated by OpenCVE AI on September 26, 2026 at 16:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypass
First Time appeared Netty
Netty netty
Weaknesses CWE-295
CPEs cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*
Vendors & Products Netty
Netty netty
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 8.7, 'vector': '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'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 2, 2026, 3:46 PM
Reserved
Sep 26, 2026, 2:33 AM
Status
Deferred
Published
Sep 26, 2026, 2:16 PM
Modified
Oct 2, 2026, 4:16 PM
Severity
Important
Public date
Sep 26, 2026, 1:23 PM