Is io.netty:netty-handler 4.0 vulnerable?
Maven · 57 releases from 4.0.0 to 4.0.56 · latest io.netty:netty-handler is 4.2.21.Final · checked 18 Nov 2026
Yes: 7 known advisories
Yes. io.netty:netty-handler 4.0.56, the last 4.0 release, is affected by 7 known security advisories (1 critical, 3 high, 3 medium), including CVE-2026-75595, CVE-2026-50010, CVE-2026-45416. 1 more affects earlier 4.0.x releases. Upgrade to 4.1.137.Final or later to fix all of them.
mvn versions:use-dep-version -Dincludes=io.netty:netty-handler -DdepVersion=4.1.137.Final -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
Advisories affecting io.netty:netty-handler 4.0.56
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
netty-handler SniHandler 16MB allocation
- Affected
- <4.1.94.Final
- Fixed in
- 4.1.94.Final
HTTP Request Smuggling in Netty
- Affected
- >=4.0.0 <4.1.45
- Fixed in
- 4.1.45
Fixed within 4.0.x, affecting earlier releases
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
Every io.netty:netty-handler 4.0.x release
Affected: 4.0.0 to 4.0.56. Latest io.netty:netty-handler: 4.2.21.Final.
| Version | Known advisories |
|---|---|
| io.netty:netty-handler 4.0.56 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.55 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.54 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.53 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.52 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.51 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.50 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.49 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.48 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.47 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.46 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.45 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.44 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.43 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.42 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.41 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.40 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.39 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.38 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.37 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2019-20445 |
| io.netty:netty-handler 4.0.36 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.35 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.34 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.33 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.32 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.31 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.30 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.29 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.28 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.27 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.26 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.25 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.24 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.23 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.22 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.21 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.20 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.19 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.18 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.17 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.16 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.15 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.14 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.13 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.12 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.11 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.10 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.9 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.8 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.7 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.6 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.5 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.4 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.3 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.2 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.1 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
| io.netty:netty-handler 4.0.0 | CVE-2026-75595, CVE-2026-75596, CVE-2026-50010, CVE-2026-45416, CVE-2026-44249, CVE-2023-34462, CVE-2016-4970, CVE-2019-20445 |
Which of your client projects are still on io.netty:netty-handler 4.0?
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.