Improper Check for Unusual or Exceptional Conditions Affecting io.netty:netty-handler package, versions [4.2.0.Final,4.2.17.Final)[,4.1.137.Final)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-IONETTY-19005879
- published20 Aug 2026
- disclosed19 Aug 2026
- creditvioletagg
Introduced: 19 Aug 2026
NewCVE-2026-75595 (opens in a new tab)How to fix?
Upgrade io.netty:netty-handler to version 4.2.17.Final, 4.1.137.Final or higher.
Overview
io.netty:netty-handler is a library that provides an asynchronous event-driven network application framework and tools for rapid development of maintainable high performance and high scalability protocol servers and clients. In other words, Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server.
Affected versions of this package are vulnerable to Improper Check for Unusual or Exceptional Conditions through the SslClientHelloHandler.decode ClientHello parser in handler/src/main/java/io/netty/handler/ssl/SslClientHelloHandler.java. An attacker can bypass per-SNI mTLS selection by sending a fragmented TLS ClientHello whose 4-byte handshake header spans multiple records, causing parsing to fail and the connection to fall back to the default SslContext. This breaks deployments that rely on SNI-driven SslContext selection as the only client-certificate check: the request reaches the default TLS configuration instead of the intended SNI-specific context, allowing an unauthenticated client to complete a connection where mTLS was expected.