Is io.netty:netty-handler 4.1 vulnerable?
Maven · 142 releases from 4.1.0 to 4.1.141 · latest io.netty:netty-handler is 4.2.21.Final · checked 18 Nov 2026
No known advisories in the last release
io.netty:netty-handler 4.1.141, the last 4.1 release, has no known advisories. 11 advisories affect earlier 4.1.x releases, so update to 4.1.141.
mvn versions:use-dep-version -Dincludes=io.netty:netty-handler -DdepVersion=4.1.141 -DforceVersion=trueIs your project on an affected io.netty:netty-handler?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 4.1.x, affecting earlier releases
Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext
- Affected
- >=4.2.0.Final <4.2.17.Final · <4.1.137.Final
- Fixed in
- 4.1.137.Final, 4.2.17.Final
Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing
- Affected
- >=4.2.0.Final <4.2.17.Final · <4.1.137.Final
- Fixed in
- 4.1.137.Final, 4.2.17.Final
Netty: Wrapping plain trust manager silently disables hostname verification
- Affected
- >=4.2.0.Final <4.2.15.Final · <4.1.135.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
Netty: SNI handler pre-allocates up to 16 MiB from nine attacker bytes
- Affected
- >=4.2.0.Final <4.2.15.Final · <4.1.135.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
Netty has an IPv6 Subnet Filter Bypass via Incorrect Comparator Masking
- Affected
- >=4.2.0.Final <4.2.15.Final · <4.1.135.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
SslHandler doesn't correctly validate packets which can lead to native crash when using native SSLEngine
- Affected
- >=4.1.91.Final <4.1.118.Final
- Fixed in
- 4.1.118.Final
netty-handler SniHandler 16MB allocation
- Affected
- <4.1.94.Final
- Fixed in
- 4.1.94.Final
Loop with Unreachable Exit Condition in Netty
- Affected
- >=4.0.0.Alpha1 <4.0.37.Final · >=4.1.0.Beta1 <4.1.1.Final
- Fixed in
- 4.0.37.Final, 4.1.1.Final
Denial of Service in Netty
- Affected
- >=4.1.0 <4.1.46
- Fixed in
- 4.1.46
HTTP Request Smuggling in Netty
- Affected
- >=4.1.43 <4.1.45
- Fixed in
- 4.1.45
HTTP Request Smuggling in Netty
- Affected
- >=4.0.0 <4.1.45
- Fixed in
- 4.1.45
Every io.netty:netty-handler 4.1.x release
Affected: 4.1.82 to 4.1.136. 4.1.137 and later are not affected. Latest io.netty:netty-handler: 4.2.21.Final.
| Version | Known advisories |
|---|---|
| io.netty:netty-handler 4.1.141 | None |
| io.netty:netty-handler 4.1.140 | None |
| io.netty:netty-handler 4.1.139 | None |
| io.netty:netty-handler 4.1.138 | None |
| io.netty:netty-handler 4.1.137 | None |
| io.netty:netty-handler 4.1.136 | CVE-2026-75595, CVE-2026-75596 |
| io.netty:netty-handler 4.1.135 | CVE-2026-75595, CVE-2026-75596 |
| io.netty:netty-handler 4.1.134 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.133 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.132 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.131 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.130 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.129 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.128 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.127 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.126 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.125 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.124 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.123 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.122 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.121 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.120 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.119 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.118 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249 |
| io.netty:netty-handler 4.1.117 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.116 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.115 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.114 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.113 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.112 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.111 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.110 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.109 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.108 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.107 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.106 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.105 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.104 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.103 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.102 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.101 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.100 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.99 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.98 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.97 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.96 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.95 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.94 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970 |
| io.netty:netty-handler 4.1.93 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970, CVE-2023-34462 |
| io.netty:netty-handler 4.1.92 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970, CVE-2023-34462 |
| io.netty:netty-handler 4.1.91 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2025-24970, CVE-2023-34462 |
| io.netty:netty-handler 4.1.90 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.89 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.88 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.87 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.86 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.85 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.84 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.83 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
| io.netty:netty-handler 4.1.82 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462 |
Which of your client projects are still on io.netty:netty-handler 4.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact io.netty:netty-handler version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other io.netty:netty-handler versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.