Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-6jv9-x5w9-2ccm

Netty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator

CVSS 8.7 HighEPSS 0.0074 · 54th percentile

Published by the GitHub Advisory Database at 11 Jun 2026, 13:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-codec-redisMaven>=4.2.0.Final, <4.2.15.Final || <4.1.135.Final4.2.15.Final, 4.1.135.Final
Identifiers
GHSA-6jv9-x5w9-2ccm · CVE-2026-48006
Weakness (CWE)
CWE-401 · CWE-772
Tags
Published
11 Jun 2026
Updated
18 Sept 2026

Machine-written summary

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

Netty's netty-codec-redis package, versions 4.2.0.Final before 4.2.15.Final and 4.1.x before 4.1.135.Final, has a memory leak in its RedisArrayAggregator handler. When a Redis pipeline connection closes before an array aggregate completes, pooled direct-memory buffers are never released. A remote network peer can repeatedly open and drop connections to exhaust the shared direct-memory pool, causing allocation failures for other Netty channels in the process. Upgrade to 4.2.15.Final or 4.1.135.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
8.7 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0074, the 54th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 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.