Netty Codec Http
Approved changes feed: RSS · Atom
cpe:2.3:a:io.netty:netty-codec-http:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Io.Netty (7808cde2-d5c9-5fd6-931a-aabaf07399fd) |
|---|---|
| Product | Netty Codec Http (15513c15-c6d4-5f0f-8260-b11cdd142e0b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42587 |
vulnerable | 2026-06-08 08:03:16.537764 |
Netty: HttpContentDecompressor maxAllocation bypass via Content-Encoding: br/zstd/snappy enables decompression bomb DoS
HIGH (7.5)
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpContentDecompressor accepts a maxAllocation parameter to limit decompression buffer size and prevent decompression bomb attacks. This limit is correctly enforced for gzip and deflate encodings via ZlibDecoder, but is silently ignored when the content encoding is br (Brotli), zstd, or snappy. An attacker can bypass the configured decompression limit by sending a compressed payload with Content-Encoding: br instead of Content-Encoding: gzip, causing unbounded memory allocation and out-of-memory denial of service. The same vulnerability exists in DelegatingDecompressorFrameListener for HTTP/2 connections. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Published: 2026-05-13T18:22:21.699Z
Updated: 2026-08-13T12:04:31.543Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42585 |
vulnerable | 2026-06-08 08:03:16.535190 |
Netty: HTTP Request Smuggling due to malformed Transfer-Encoding
MEDIUM (6.5)
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty incorrectly parses malformed Transfer-Encoding, enabling request smuggling attacks. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Published: 2026-05-13T18:12:39.586Z
Updated: 2026-05-15T20:34:21.305Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42584 |
vulnerable | 2026-06-08 08:03:16.534595 |
Netty: HttpClientCodec response desynchronization
HIGH (7.3)
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpClientCodec pairs each inbound response with an outbound request by queue.poll() once per response, including for 1xx. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message’s body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Published: 2026-05-13T18:10:48.437Z
Updated: 2026-08-21T12:13:05.400Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42580 |
vulnerable | 2026-06-08 08:03:16.529439 |
Netty: HTTP Request Smuggling due to incorrect chunk size parsing
MEDIUM (6.5)
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty's chunk size parser silently overflows int, enabling request smuggling attacks. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Published: 2026-05-13T18:04:03.690Z
Updated: 2026-05-14T18:21:13.322Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.