Is io.netty:netty-codec-http2 4.2 vulnerable?
Maven · 22 releases from 4.2.0 to 4.2.21 · 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.2.21, the last 4.2 release, has no known advisories. 8 advisories affect earlier 4.2.x releases, so update to 4.2.21.
mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http2 -DdepVersion=4.2.21 -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.2.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
Every io.netty:netty-codec-http2 4.2.x release
Affected: 4.2.0 to 4.2.15. 4.2.16 and later are not affected. Latest io.netty:netty-codec-http2: 4.2.21.Final.
| Version | Known advisories |
|---|---|
| io.netty:netty-codec-http2 4.2.21 | None |
| io.netty:netty-codec-http2 4.2.20 | None |
| io.netty:netty-codec-http2 4.2.19 | None |
| io.netty:netty-codec-http2 4.2.18 | None |
| io.netty:netty-codec-http2 4.2.17 | None |
| io.netty:netty-codec-http2 4.2.16 | None |
| io.netty:netty-codec-http2 4.2.15 | CVE-2026-56819, CVE-2026-59900 |
| io.netty:netty-codec-http2 4.2.14 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244 |
| io.netty:netty-codec-http2 4.2.13 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244 |
| io.netty:netty-codec-http2 4.2.12 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587 |
| io.netty:netty-codec-http2 4.2.11 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587 |
| io.netty:netty-codec-http2 4.2.10 | 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.2.9 | 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.2.8 | 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.2.7 | 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.2.6 | 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.2.5 | 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.2.4 | 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.2.3 | 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.2.2 | 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.2.1 | 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.2.0 | CVE-2026-56819, CVE-2026-59900, CVE-2026-50560, CVE-2026-48043, CVE-2026-47244, CVE-2026-42587, CVE-2026-33871, CVE-2025-55163 |
Which of your client projects are still on io.netty:netty-codec-http2 4.2?
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.