CVE-2026-75595Network attack vector

mTLS bypass via fragmented ClientHello

Published Aug 19, 2026 · Updated Aug 20, 2026

Authentication bypass in Netty before 4.1.137.Final and 4.2.17.Final allows remote attackers to bypass mTLS via a fragmented ClientHello. In io.netty.handler.ssl.SslClientHelloHandler#decode, the pre-read guard checks for the four-byte handshake header at the wrong offset, and the resulting exception path calls select(ctx, null), falling back from the SNI-selected SslContext to the default context. Exploitation requires deployments that rely on per-SNI clientAuth=REQUIRE as the only client-certificate gate while the default context accepts missing certificates and no application-layer certificate check blocks the request.

CVSS severity9.1
Critical
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in Netty before 4.1.137.Final and 4.2.17.Final allows remote attackers to bypass mTLS via a fragmented ClientHello. In io.netty.handler.ssl.SslClientHelloHandler#decode, the pre-read guard checks for the four-byte handshake header at the wrong offset, and the resulting exception path calls select(ctx, null), falling back from the SNI-selected SslContext to the default context. Exploitation requires deployments that rely on per-SNI clientAuth=REQUIRE as the only client-certificate gate while the default context accepts missing certificates and no application-layer certificate check blocks the request.

The record

CVE
CVE-2026-75595
Published
Aug 19, 2026
Updated
Aug 20, 2026
Vendor
The Netty Project
Product
Netty
Classifications
CWE-754, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 4.1.137.Final
  2. Affected versionversion=>= 4.2.0.Final, < 4.2.17.Final

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Netty Project · Nettyversion=< 4.1.137.Final; version=>= 4.2.0.Final, < 4.2.17.Final

Published CVSS scores

9.1GitHub, Inc.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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-754Improper Check for Unusual or Exceptional Conditions
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo