Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-q4f6-jm68-57ww

Netty: [HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service

CVSS 6.9 MediumEPSS 0.0061 · 49th percentile

Published by the GitHub Advisory Database at 22 Jul 2026, 21:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-codec-httpMaven>=4.2.0.Final, <4.2.16.Final || <4.1.136.Final4.2.16.Final, 4.1.136.Final
Identifiers
GHSA-q4f6-jm68-57ww · CVE-2026-59899
Weakness (CWE)
CWE-770
Tags
Published
22 Jul 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Netty's netty-codec-http package, versions from 4.2.0.Final before 4.2.16.Final and from 4.1.0 before 4.1.136.Final (per the affected range given), has an unbounded per-connection queue in HttpContentEncoder and its subclass HttpContentCompressor. An attacker who can send HTTP/1.1 pipelined requests faster than the application writes responses can make this queue grow without limit, causing resource exhaustion and denial of service. Upgrade to 4.2.16.Final or 4.1.136.Final.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0061, the 49th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.