# Netty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator Advisory record · `GHSA-6jv9-x5w9-2ccm` - **Identifiers:** `GHSA-6jv9-x5w9-2ccm` · `CVE-2026-48006` - **State:** Confirmed - **Severity:** CVSS 8.7 High - **Critical:** No - **Weakness (CWE):** [CWE-401](https://cwe.mitre.org/data/definitions/401.html) · [CWE-772](https://cwe.mitre.org/data/definitions/772.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) - **Published:** 11 Jun 2026 - **Updated:** 18 Sept 2026 - **Reviewed by a person:** No 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. ## Affected packages - `io.netty:netty-codec-redis` (Maven): affected `>=4.2.0.Final, <4.2.15.Final || <4.1.135.Final`; fixed in `4.2.15.Final`, `4.1.135.Final` ## 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 - 8.7 High, CVSS 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`, from 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 - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6jv9-x5w9-2ccm) ## Sources - [GitHub Advisory Database: GHSA-6jv9-x5w9-2ccm](https://github.com/advisories/GHSA-6jv9-x5w9-2ccm) - [OSV: GHSA-6jv9-x5w9-2ccm](https://osv.dev/vulnerability/GHSA-6jv9-x5w9-2ccm) - - - - - - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .