Is io.netty:netty-codec-http 4.2 vulnerable?
Maven · 22 releases from 4.2.0 to 4.2.21 · latest io.netty:netty-codec-http is 4.2.21.Final · checked 18 Nov 2026
No known advisories in the last release
io.netty:netty-codec-http 4.2.21, the last 4.2 release, has no known advisories. 18 advisories affect earlier 4.2.x releases, so update to 4.2.21.
mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http -DdepVersion=4.2.21 -DforceVersion=trueIs your project on an affected io.netty:netty-codec-http?
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 Vulnerable to Cache Poisoning and Information Disclosure via CORS Vary Header Overwrite
- Affected
- >=4.2.0.Final <4.2.17.Final · <4.1.137.Final
- Fixed in
- 4.1.137.Final, 4.2.17.Final
Netty: CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder
- Affected
- >=4.2.0.Final <4.2.16.Final · <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty: [HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service
- Affected
- >=4.2.0.Final <4.2.16.Final · <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty: WebSockets V07/V08 handshaker missing Connection/Upgrade validation
- Affected
- >=4.2.0.Final <4.2.16.Final · <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty: Security Control Bypass via CORS Short-Circuit Failure
- Affected
- >=4.2.0.Final <4.2.16.Final · <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty: [SpdyHttpDecoder] ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion
- Affected
- >=4.2.0.Final <4.2.16.Final · >=4.1.0.Final <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty SPDY zlib header block continues decoded expansion after maxHeaderSize truncation
- Affected
- >=4.2.0.Final <4.2.16.Final · >=4.1.0.Final <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty SPDY SETTINGS frame count materializes unbounded settings map
- Affected
- >=4.2.0.Final <4.2.16.Final · >=4.1.0.Final <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty: HttpObjectDecoder skips arbitrary initial control characters when only initial CRLF characters are permitted
- 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 vulnerable to HTTP Request Smuggling due to malformed Transfer-Encoding
- Affected
- >=4.2.0.Alpha1 <4.2.13.Final · <4.1.133.Final
- Fixed in
- 4.1.133.Final, 4.2.13.Final
Netty has HttpClientCodec response desynchronization
- 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/1.0 TE+CL Coexistence Bypasses Smuggling Sanitization
- Affected
- >=4.2.0.Alpha1 <4.2.13.Final · <4.1.133.Final
- Fixed in
- 4.1.133.Final, 4.2.13.Final
Netty vulnerable to HTTP Request Smuggling due to incorrect chunk size parsing
- Affected
- >=4.2.0.Alpha1 <4.2.13.Final · <4.1.133.Final
- Fixed in
- 4.1.133.Final, 4.2.13.Final
Netty: Start-Line Injection in DefaultHttpRequest.setUri() Allows HTTP Request Smuggling and RTSP Request Injection
- Affected
- <4.1.133.Final · >=4.2.0.Alpha1 <4.2.13.Final
- Fixed in
- 4.1.133.Final, 4.2.13.Final
Netty: HTTP Request Smuggling via Chunked Extension Quoted-String Parsing
- Affected
- <4.1.132.Final · >=4.2.0.Alpha1 <4.2.10.Final
- Fixed in
- 4.1.132.Final, 4.2.10.Final
Netty has a CRLF Injection vulnerability in io.netty.handler.codec.http.HttpRequestEncoder
- Affected
- >=4.2.0.Alpha1 <4.2.8.Final · <4.1.129.Final
- Fixed in
- 4.1.129.Final, 4.2.8.Final
Netty vulnerable to request smuggling due to incorrect parsing of chunk extensions
- Affected
- <4.1.125.Final · >=4.2.0.Alpha1 <4.2.5.Final
- Fixed in
- 4.1.125.Final, 4.2.5.Final
Every io.netty:netty-codec-http 4.2.x release
Affected: 4.2.0 to 4.2.16. 4.2.17 and later are not affected. Latest io.netty:netty-codec-http: 4.2.21.Final.
| Version | Known advisories |
|---|---|
| io.netty:netty-codec-http 4.2.21 | None |
| io.netty:netty-codec-http 4.2.20 | None |
| io.netty:netty-codec-http 4.2.19 | None |
| io.netty:netty-codec-http 4.2.18 | None |
| io.netty:netty-codec-http 4.2.17 | None |
| io.netty:netty-codec-http 4.2.16 | CVE-2026-59903 |
| io.netty:netty-codec-http 4.2.15 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 |
| io.netty:netty-codec-http 4.2.14 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020 |
| io.netty:netty-codec-http 4.2.13 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020 |
| io.netty:netty-codec-http 4.2.12 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417 |
| io.netty:netty-codec-http 4.2.11 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417 |
| io.netty:netty-codec-http 4.2.10 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417 |
| io.netty:netty-codec-http 4.2.9 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870 |
| io.netty:netty-codec-http 4.2.8 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870 |
| io.netty:netty-codec-http 4.2.7 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735 |
| io.netty:netty-codec-http 4.2.6 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735 |
| io.netty:netty-codec-http 4.2.5 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735 |
| io.netty:netty-codec-http 4.2.4 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735, CVE-2025-58056 |
| io.netty:netty-codec-http 4.2.3 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735, CVE-2025-58056 |
| io.netty:netty-codec-http 4.2.2 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735, CVE-2025-58056 |
| io.netty:netty-codec-http 4.2.1 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735, CVE-2025-58056 |
| io.netty:netty-codec-http 4.2.0 | CVE-2026-59903, CVE-2026-59921, CVE-2026-59899, CVE-2026-59898, CVE-2026-56746, CVE-2026-56745, CVE-2026-55833, CVE-2026-55831, CVE-2026-50020, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-33870, CVE-2025-67735, CVE-2025-58056 |
Which of your client projects are still on io.netty:netty-codec-http 4.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact io.netty:netty-codec-http version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other io.netty:netty-codec-http 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.