Vulnerabilities in pkg:maven/io.netty/netty-handler
PACKAGECVE-2026-75595 is a CRITICAL sni routing bypass vulnerability (CWE-754: Improper Check for Unusual or Exceptional Conditions) affecting Netty libraries in the Maven ecosystem. The issue involves sni routing bypass via fragmented tls clienthello causing fallback to default sslcontext. Remediation is available by upgrading affected packages to version 4.2.17.Final, 4.1.137.Final.
pkg:maven/io.netty/netty-handler
Vulnerability advisories affecting package pkg:maven/io.netty/netty-handler. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-c4c3-7fpv-j4q5 | CVE-2026-75595 | CRITICAL | Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext |
| GHSA-fccg-mwvh-qqg4 | CVE-2026-75596 | MODERATE | Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing |
| GHSA-c653-97m9-rcg9 | CVE-2026-50010 | HIGH | Netty: Wrapping plain trust manager silently disables hostname verification |
| GHSA-x4gw-5cx5-pgmh | CVE-2026-45416 | HIGH | Netty: SNI handler pre-allocates up to 16 MiB from nine attacker bytes |
| GHSA-3qp7-7mw8-wx86 | CVE-2026-44249 | HIGH | Netty has an IPv6 Subnet Filter Bypass via Incorrect Comparator Masking |
| GHSA-4g8c-wm8x-jfhw | CVE-2025-24970 | HIGH | SslHandler doesn't correctly validate packets which can lead to native crash when using native SSLEngine |
| GHSA-6mjq-h674-j845 | CVE-2023-34462 | MODERATE | netty-handler SniHandler 16MB allocation |
| GHSA-57m8-f3v5-hm5m | CVE-2023-4586 | MODERATE | Withdrawn Advisory: Netty-handler does not validate host names by default |
| GHSA-rv63-gqm8-9w8q | CVE-2016-4970 | HIGH | Loop with Unreachable Exit Condition in Netty |
| GHSA-9959-6p3m-wxpc | CVE-2014-3488 | MODERATE | Denial of service in Netty |
| GHSA-p2v9-g2qv-p635 | CVE-2019-20445 | MODERATE | HTTP Request Smuggling in Netty |
| GHSA-ff2w-cq2g-wv5f | CVE-2020-7238 | HIGH | HTTP Request Smuggling in Netty |
| GHSA-mm9x-g8pc-w292 | CVE-2020-11612 | HIGH | Denial of Service in Netty |
CVE-2026-75595 at a Glance
How to Fix CVE-2026-75595
To remediate this vulnerability, upgrade all affected Netty dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-handler</artifactId>
<version>4.2.17.Final</version>
</dependency>
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-handler</artifactId>
<version>4.1.137.Final</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=io.netty
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-75595, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=io.netty
Analyze the terminal output to locate any version of Netty in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.2.17.Final), your application is affected.
Note: The mvn dependency:tree -Dincludes=io.netty command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-754: Improper Check for Unusual or Exceptional Conditions, where the product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. In Netty, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-75595 Affected Netty Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
io.netty:netty-handler
|
Maven |
≥ 4.2.0.Final
< 4.2.17.Final
|
4.2.17.Final
|
|
io.netty:netty-handler
|
Maven |
< 4.1.137.Final
|
4.1.137.Final
|
References
Frequently Asked Questions
What is CVE-2026-75595?
Which Netty versions are affected?
What version fixes CVE-2026-75595?
Is netty-handler affected?
What CWE is associated with CVE-2026-75595?
How can I check Maven dependencies for CVE-2026-75595?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-c4c3-7fpv-j4q5",
"modified" : "2026-09-08T18:16:14Z",
"published" : "2026-09-08T18:16:14Z",
"aliases" : [ "CVE-2026-75595" ],
"summary" : "Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext",
"details" : "### Summary\nA fragmented TLS ClientHello whose handshake header spans multiple records makes Netty silently fall back to the default SslContext; where per-SNI selection is the sole mTLS gate, an unauthenticated attacker can bypass the route's mTLS requirement.\n\n### Details\nIn `io.netty.handler.ssl.SslClientHelloHandler#decode` the guard that should wait for the 4-byte handshake header checks the wrong offset - it ignores the 5-byte record header that precedes it - and therefore never fires:\n\n```java\nif (handshakeLength == -1) {\n if (readerIndex + 4 > endOffset) {\n // Need more data to read HandshakeType and handshakeLength (4 bytes)\n return;\n }\n```\n\nWhen the first record's payload is < 4 bytes, `handshakeLength = in.getUnsignedMedium(readerIndex + SslUtils.SSL_RECORD_HEADER_LENGTH + 1);` leads to `IndexOutOfBoundsException `. That is caught by the generic `catch (Exception)` block, which calls `select(ctx, null)` - this is the default `SslContext`. Fallback to default on parse failure is a problem when per-SNI selection is the sole mTLS gate.\n\n### Impact\nSNI routing bypass. Escalates to an unauthenticated mTLS bypass only when:\n- mTLS is enforced solely via per-SNI SslContext (clientAuth=REQUIRE)\n- the default/fallback SslContext is permissive (clientAuth=NONE/OPTIONAL)\n- no secondary peer-certificate verification exists at the application layer.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "io.netty:netty-handler"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.2.0.Final"
}, {
"fixed" : "4.2.17.Final"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.2.16.Final"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "io.netty:netty-handler"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "4.1.137.Final"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.1.136.Final"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/netty/netty/security/advisories/GHSA-c4c3-7fpv-j4q5"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-75595"
}, {
"type" : "WEB",
"url" : "https://github.com/netty/netty/pull/17213"
}, {
"type" : "WEB",
"url" : "https://github.com/netty/netty/pull/17217"
}, {
"type" : "WEB",
"url" : "https://github.com/netty/netty/commit/1b5abc6443b63726c72cdd285af2feb7ddbb8ff7"
}, {
"type" : "WEB",
"url" : "https://github.com/netty/netty/commit/9e0519239108a69b7e9bbc5e9182ee139a0d7961"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/netty/netty"
}, {
"type" : "WEB",
"url" : "https://github.com/netty/netty/releases/tag/netty-4.1.137.Final"
}, {
"type" : "WEB",
"url" : "https://github.com/netty/netty/releases/tag/netty-4.2.17.Final"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-475", "CWE-754" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-08T18:16:14Z",
"nvd_published_at" : "2026-08-19T21:17:37Z"
}
}