CVE-2026-75595CWE-754

CVE-2026-75595

Critical · published August 20, 2026

CVSS v3.1
9.1
EPSS
0%
Percentile
19.1
In the wild
Unconfirmed
What it is

Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Fina and 4.2.17.Final, io.netty.handler.ssl.SslClientHelloHandler#decode checks the wrong offset before reading the four-byte TLS handshake header, so a ClientHello whose handshake header spans records can cause an IndexOutOfBoundsException and invoke select(ctx, null). This selects the default SslContext instead of the SNI-specific context. In deployments where per-SNI clientAuth=REQUIRE is the sole mutual TLS gate, the default SslContext uses clientAuth=NONE or clientAuth=OPTIONAL, and no application-layer certificate verification exists, an unauthenticated remote attacker can bypass the protected route's mutual TLS requirement. This issue is fixed in versions 4.1.137.Final and 4.2.17.Final.

The record
Technical detail
CVSS v3.1
9.1 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0
9.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS
0.00277 · 19.1th percentile
Weakness
CWE-754 · Improper Check for Unusual or Exceptional Conditions
Published
2026-08-20T01:17Z
Affected products (2)
ProductVersionsFixed in
netty/netty< 4.1.1374.1.137
netty/netty≥ 4.2.0, < 4.2.174.2.17
References (7)
EPSS history
Timeline
  • 19 AUG 21:00Z
    Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext
    cvelistv5