CVE-2026-100665: Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypass

Published Sep 26, 2026
·
Updated

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.

Affected Software

1 affected component
Netty Netty>=4.2.11.Final<4.2.18.Final

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Netty to a version that resolves this vulnerability.

    Fixed in 4.2.18.Final

Event History

Sep 26, 2026
CVE Published
via MITRE·01:23 PM
Data Sourced
via MITRE·01:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

QUIC clients using Netty 4.2.11.Final through 4.2.17.Final are exposed when they use a plain X509TrustManager and have HTTPS endpoint identification configured. The affected verification path fails to perform hostname authentication in that configuration.

2

What does an attacker need to exploit the vulnerability?

The attacker must be on the network path to the QUIC client and be able to present a certificate chain accepted by the client’s plain trust manager for a hostname other than the intended endpoint. No client-side privileges or user interaction are required.

3

What is the security impact of successful exploitation?

An attacker can bypass hostname authentication for affected QUIC clients, allowing a certificate valid for the wrong hostname to be accepted. The described impact is exposure of confidential information; integrity and availability impacts are not specified.

4

How can I determine whether a client is affected?

Check whether the application uses Netty QUIC with a plain X509TrustManager and HTTPS endpoint identification, and whether its Netty version is 4.2.11.Final through 4.2.17.Final. Clients outside that version range are not identified as affected by the provided information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203