CVE-2026-59899

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 22, 2026

Last Modified

August 6, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
Patch available. Sources: github, github_release.
github_release Patch Available

netty-4.2.16.Final

Patch available: netty/netty netty-4.2.16.Final

https://github.com/netty/netty/releases/tag/netty-4.2.16.Final
github_release Patch Available

netty-4.1.136.Final

Patch available: netty/netty netty-4.1.136.Final

https://github.com/netty/netty/releases/tag/netty-4.1.136.Final
github Patch Available

[HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-q4f6-jm68-57ww

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcryostat/jfr-datasource-rhel9:4.2.0-142026-09-16redhat
redhatnetty-codec-http2026-09-10redhat
redhatrhoai/odh-trustyai-service-rhel9:17881986812026-09-08redhat
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-codec-http4.0.0.Alpha1 ... 4.1.99.Final (229 versions)4.1.136.Final

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 86× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 172 total refreshes for this CVE.

  1. 2026-09-18 22:40 UTCEG score recompute
  2. 2026-09-18 22:40 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:10 UTCEG score recompute
  5. 2026-09-18 03:10 UTCVendor advisory
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-17 02:06 UTCEG score recompute
  8. 2026-09-17 02:06 UTCVendor advisory
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 06:58 UTCEG score recompute
  11. 2026-09-16 06:58 UTCVendor advisory
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 03:11 UTCEPSS rescore
  14. 2026-09-14 10:24 UTCVendor advisory
  15. 2026-09-13 22:25 UTCEG score recompute
  16. 2026-09-13 22:25 UTCVendor advisory
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-13 09:13 UTCVendor advisory
  19. 2026-09-12 21:14 UTCEG score recompute
  20. 2026-09-12 21:14 UTCVendor advisory
  21. 2026-09-12 09:15 UTCVendor advisory
  22. 2026-09-11 21:15 UTCEG score recompute
  23. 2026-09-11 21:15 UTCVendor advisory
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 09:14 UTCVendor advisory
Show 75 more
  1. 2026-09-10 21:15 UTCEG score recompute
  2. 2026-09-10 21:15 UTCVendor advisory
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-09 09:11 UTCEG score recompute
  5. 2026-09-09 09:11 UTCVendor advisory
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 21:39 UTCEG score recompute
  8. 2026-09-07 21:39 UTCVendor advisory
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 08:40 UTCVendor advisory
  12. 2026-09-05 19:33 UTCEG score recompute
  13. 2026-09-05 19:33 UTCVendor advisory
  14. 2026-09-05 07:07 UTCEG score recompute
  15. 2026-09-05 07:07 UTCVendor advisory
  16. 2026-09-04 13:39 UTCEG score recompute
  17. 2026-09-04 13:39 UTCVendor advisory
  18. 2026-09-04 05:07 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 23:37 UTCEG score recompute
  21. 2026-09-01 23:37 UTCVendor advisory
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-31 00:54 UTCEG score recompute
  25. 2026-08-31 00:54 UTCVendor advisory
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 12:55 UTCEG score recompute
  28. 2026-08-30 12:55 UTCVendor advisory
  29. 2026-08-30 01:22 UTCEPSS rescore
  30. 2026-08-30 00:50 UTCEG score recompute
  31. 2026-08-30 00:50 UTCVendor advisory
  32. 2026-08-28 21:42 UTCEPSS rescore
  33. 2026-08-27 22:15 UTCEG score recompute
  34. 2026-08-27 22:15 UTCVendor advisory
  35. 2026-08-27 14:25 UTCEPSS rescore
  36. 2026-08-27 10:16 UTCVendor advisory
  37. 2026-08-26 21:17 UTCEG score recompute
  38. 2026-08-26 21:17 UTCVendor advisory
  39. 2026-08-26 14:46 UTCEPSS rescore
  40. 2026-08-26 08:54 UTCVendor advisory
  41. 2026-08-25 20:54 UTCEG score recompute
  42. 2026-08-25 20:54 UTCVendor advisory
  43. 2026-08-25 13:49 UTCEPSS rescore
  44. 2026-08-25 08:55 UTCVendor advisory
  45. 2026-08-24 20:54 UTCEG score recompute
  46. 2026-08-24 20:54 UTCVendor advisory
  47. 2026-08-24 08:55 UTCVendor advisory
  48. 2026-08-23 20:53 UTCVendor advisory
  49. 2026-08-23 08:53 UTCEG score recompute
  50. 2026-08-23 08:53 UTCVendor advisory
  51. 2026-08-23 00:19 UTCEPSS rescore
  52. 2026-08-22 20:54 UTCVendor advisory
  53. 2026-08-22 08:55 UTCEG score recompute
  54. 2026-08-22 08:55 UTCVendor advisory
  55. 2026-08-21 23:49 UTCEPSS rescore
  56. 2026-08-21 20:56 UTCVendor advisory
  57. 2026-08-21 08:57 UTCEG score recompute
  58. 2026-08-21 08:57 UTCVendor advisory
  59. 2026-08-20 22:55 UTCEPSS rescore
  60. 2026-08-20 20:56 UTCVendor advisory
  61. 2026-08-20 08:57 UTCVendor advisory
  62. 2026-08-19 20:58 UTCEG score recompute
  63. 2026-08-19 20:58 UTCVendor advisory
  64. 2026-08-19 17:04 UTCEPSS rescore
  65. 2026-08-19 08:58 UTCVendor advisory
  66. 2026-08-18 20:52 UTCEG score recompute
  67. 2026-08-18 20:52 UTCVendor advisory
  68. 2026-08-18 13:48 UTCEPSS rescore
  69. 2026-08-18 08:53 UTCVendor advisory
  70. 2026-08-17 20:26 UTCEG score recompute
  71. 2026-08-17 20:26 UTCVendor advisory
  72. 2026-08-17 13:47 UTCEPSS rescore
  73. 2026-08-17 08:25 UTCVendor advisory
  74. 2026-08-16 20:26 UTCEG score recompute
  75. 2026-08-16 20:26 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-59899?
CVE-2026-59899 is a high vulnerability published on July 22, 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…
When was CVE-2026-59899 disclosed?
CVE-2026-59899 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59899 actively exploited?
CVE-2026-59899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.1% of all scored CVEs.
What is the CVSS score of CVE-2026-59899?
CVE-2026-59899 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59899, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59899

Explore →

Is Your Infrastructure Affected by CVE-2026-59899?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.