Answer in brief
CVE-2026-59899 records a High severity (CVSS 7.5) vulnerability in Netty: [HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service. The current sources do not mark it as known exploited. The current feed maps io.netty:netty-codec-http (maven), io.netty:netty-codec-http (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps io.netty:netty-codec-http (maven), io.netty:netty-codec-http (maven). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| io.netty:netty-codec-httpmaven | >=4.2.0.Final <4.2.16.Final | 4.2.16.Final |
| io.netty:netty-codec-httpmaven | >=0 <4.1.136.Final | 4.1.136.Final |
Published upstream
Jul 22, 2026
Evidence: source:nvd:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:nvd:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, `HttpContentEncoder` (the superclass of the production handler `HttpContentCompressor`) maintains a per-channel `ArrayDeque<CharSequence>` named `acceptEncodingQueue` that accumulates attacker-controlled data without any size limit. The queue is filled on the I/O thread for every inbound HTTP request and drained only when the application later writes a non-1xx response. This creates a resource exhaustion vulnerability when an attacker exploits HTTP/1.1 pipelining to flood the connection with requests faster than the application produces responses. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.
Quoted source text, attributed separately from HOL analysis.