Skip to main content
CVE-2026-59899VulnerabilityPublished

io.netty:netty-codec-http · Netty: [HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service

Affects io.netty:netty-codec-httpSource GCVE Database

0

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.2.16.Final when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.2.16.Final, 4.1.136.Final
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade io.netty:netty-codec-http to 4.2.16.Final; io.netty:netty-codec-http to 4.1.136.Final.

Affected software

ProductAffectedFixed in
Mavenio.netty:netty-codec-httpAffected
  • >=4.2.0.Final <4.2.16.Final
Fixed in
  • 4.2.16.Final
Mavenio.netty:netty-codec-httpAffected
  • <4.1.136.Final
Fixed in
  • 4.1.136.Final

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### Impact `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.

References

Community reviews

Loading reviews…