CVE-2026-50011

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% 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, secondary
Trending — 3 sources updated 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 a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, RedisArrayAggregator pre-allocates ArrayList with initial capacity equal to the RESP array element count declared in an array header. That count is taken from the wire before the corresponding child messages exist. A small malicious header can claim a huge initial capacity. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

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
38%
KEV
Not listed

Published

June 12, 2026

Last Modified

August 12, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: github, github_release.
github Patch Available

Unbounded pre-allocation in RedisArrayAggregator from RESP array length · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-5w86-c3rq-vjj7
github_release Patch Available

netty-4.2.15.Final

Patch available: netty/netty netty-4.2.15.Final

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

netty-4.1.135.Final

Patch available: netty/netty netty-4.1.135.Final

https://github.com/netty/netty/releases/tag/netty-4.1.135.Final

Vendor Advisories for CVE-2026-50011(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-codec-redis2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el7eap2026-08-11redhat

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-redis4.1.0.Final ... 4.1.99.Final (135 versions)4.1.135.Final—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 102× 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 173 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50011?
CVE-2026-50011 is a high vulnerability published on June 12, 2026. Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, RedisArrayAggregator pre-allocates ArrayList with initial capacity equal to the RESP array element count declared in an array header. That count is taken from…
When was CVE-2026-50011 disclosed?
CVE-2026-50011 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50011 actively exploited?
CVE-2026-50011 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 62.0% of all scored CVEs.
What is the CVSS score of CVE-2026-50011?
CVE-2026-50011 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50011, 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-50011

Explore →

Is Your Infrastructure Affected by CVE-2026-50011?

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

Start Free Scan →Browse All CVEs