CVE-2026-48006

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 47% 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
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.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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, the RedisArrayAggregator handler permanently leaks pooled direct-memory buffers when a Redis pipeline connection closes before a RESP array aggregate completes. The handler retains child messages in per-handler state (depths field) but defines no channelInactive, handlerRemoved, or exceptionCaught method to release them when the pipeline tears down. Because the leaked buffers are slices of PooledByteBufAllocator chunks, they prevent those chunks from being returned to the JVM-wide direct-memory pool. Repeated connection churn by any network peer monotonically drains this shared pool, eventually causing allocation failures on all Netty channels in the process. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

Published

June 11, 2026

Last Modified

September 18, 2026

Advisory Details (3)

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

Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-6jv9-x5w9-2ccm
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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnetty-codec-redis2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el8eap2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el9eap2026-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 rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.netty:netty-codec-redis4.1.0.Final ... 4.1.99.Final (135 versions)
  • 4.2.0.Final up to 4.2.15.Final: fixed in 4.2.15.Final
  • every version up to 4.1.135.Final: fixed in 4.1.135.Final
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 29× 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 215 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48006?
CVE-2026-48006 is a high vulnerability published on June 11, 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, the RedisArrayAggregator handler permanently leaks pooled direct-memory buffers when a Redis pipeline connection closes before a RESP array aggregate…
When was CVE-2026-48006 disclosed?
CVE-2026-48006 was first published on June 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48006 actively exploited?
CVE-2026-48006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48006?
CVE-2026-48006 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48006?
A fix for CVE-2026-48006 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48006 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48006?

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