Is io.netty:netty-codec-http2 4.1 vulnerable?
Maven · 142 releases from 4.1.0 to 4.1.141 · latest io.netty:netty-codec-http2 is 4.2.21.Final · checked 18 Nov 2026
No known advisories in the last release
io.netty:netty-codec-http2 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-codec-http2 -DdepVersion=4.1.141 -DforceVersion=trueIs your project on an affected io.netty:netty-codec-http2?
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: HTTP/2 decompression leaks ByteBuf reference count when the decompressor channel is already closed (Direct memory leak / OOM DoS)
- Affected
- >=4.2.0 <4.2.16.Final · >=4.1.0.Final <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty: [codec-http2] Lack of Host Header Deduplication in HTTP/2→HTTP/1.x Translation Leads to Request Routing Bypass
- Affected
- >=4.2.0.Final <4.2.16.Final · <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty susceptible to HTTP/2 Reset Attack with different on-the-wire signature
- Affected
- >=4.2.0.Final <4.2.15.Final · <4.1.135.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
netty-codec-http2: ByteBuf Reference-Count Leak in DelegatingDecompressorFrameListener Leads to Memory Exhaustion
- Affected
- <4.1.135.Final · >=4.2.0.Alpha1 <4.2.15.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced
- Affected
- >=4.2.0.Final <4.2.15.Final · <4.1.135.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
Netty: HttpContentDecompressor maxAllocation bypass when Content-Encoding set to br/zstd/snappy leads to decompression bomb DoS
- Affected
- >=4.2.0.Alpha1 <4.2.13.Final · <4.1.133.Final
- Fixed in
- 4.1.133.Final, 4.2.13.Final
Netty HTTP/2 CONTINUATION Frame Flood DoS via Zero-Byte Frame Bypass
- Affected
- <4.1.132.Final · >=4.2.0.Alpha1 <4.2.11.Final
- Fixed in
- 4.1.132.Final, 4.2.11.Final
Netty affected by MadeYouReset HTTP/2 DDoS vulnerability
- Affected
- >=4.2.0.Alpha1 <4.2.4.Final · <4.1.124.Final
- Fixed in
- 4.1.124.Final, 4.2.4.Final
io.netty:netty-codec-http2 vulnerable to HTTP/2 Rapid Reset Attack
- Affected
- <4.1.100.Final
- Fixed in
- 4.1.100.Final
Possible request smuggling in HTTP/2 due missing validation of content-length
- Affected
- >=4.0.0 <4.1.61.Final
- Fixed in
- 4.1.61.Final
Possible request smuggling in HTTP/2 due missing validation
- Affected
- >=4.0.0 <4.1.60.Final
- Fixed in
- 4.1.60.Final
Every io.netty:netty-codec-http2 4.1.x release
Affected: 4.1.82 to 4.1.135. 4.1.136 and later are not affected. Latest io.netty:netty-codec-http2: 4.2.21.Final.
| Version | Known advisories |
|---|---|
| io.netty:netty-codec-http2 4.1.141 | None |
| io.netty:netty-codec-http2 4.1.140 | None |
| io.netty:netty-codec-http2 4.1.139 | None |
| io.netty:netty-codec-http2 4.1.138 | None |
| io.netty:netty-codec-http2 4.1.137 | None |
| io.netty:netty-codec-http2 4.1.136 | None |
| io.netty:netty-codec-http2 4.1.135 | CVE-2026-56819, CVE-2026-59900 |
| io.netty:netty-codec-http2 4.1.134 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244 |
| io.netty:netty-codec-http2 4.1.133 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244 |
| io.netty:netty-codec-http2 4.1.132 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587 |
| io.netty:netty-codec-http2 4.1.131 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.130 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.129 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.128 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.127 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.126 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.125 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.124 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871 |
| io.netty:netty-codec-http2 4.1.123 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.122 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.121 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.120 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.119 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.118 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.117 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.116 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.115 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.114 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.113 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.112 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.111 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.110 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.109 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.108 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.107 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.106 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.105 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.104 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.103 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.102 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.101 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.100 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
| io.netty:netty-codec-http2 4.1.99 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.98 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.97 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.96 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.95 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.94 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.93 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.92 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.91 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.90 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.89 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.88 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.87 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.86 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.85 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.84 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.83 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
| io.netty:netty-codec-http2 4.1.82 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163, GHSA-xpw8-rcwv-8f8p |
Which of your client projects are still on io.netty:netty-codec-http2 4.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact io.netty:netty-codec-http2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other io.netty:netty-codec-http2 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.