Io.netty:netty codec redis: Netty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator (CVE-2026-48006)
The Netty RedisArrayAggregator handler leaks pooled direct-memory buffers when a Redis pipeline connection closes prematurely before completing a RESP array aggregate. This occurs because the handler retains child messages in internal state but lacks lifecycle cleanup methods to release these buffers on connection teardown. The leak prevents memory chunks from returning to the JVM-wide direct-memory pool, causing gradual depletion of this shared resource. Repeated connection churn can lead to allocation failures across all Netty channels in the affected process.
AI Analysis
Technical Summary
CVE-2026-48006 describes a resource leak vulnerability in the Netty io.netty:netty-codec-redis component, specifically in the RedisArrayAggregator handler. When a Redis pipeline connection closes before a RESP array aggregate completes, pooled direct-memory buffers are permanently leaked because the handler retains child messages in its 'depths' field but does not implement channel lifecycle cleanup methods such as channelInactive, handlerRemoved, or exceptionCaught to release these buffers. Since these buffers are slices of PooledByteBufAllocator chunks, the leak prevents these chunks from being returned to the JVM-wide direct-memory pool. This leads to a monotonic drain of the shared pool under repeated connection churn, ultimately causing allocation failures on all Netty channels within the process.
Potential Impact
The vulnerability causes a denial of service condition by leaking pooled direct-memory buffers, which depletes the JVM-wide direct-memory pool. This resource exhaustion can lead to allocation failures on all Netty channels in the affected process, potentially disrupting network communications that rely on Netty. There are no known exploits in the wild currently.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Users should monitor vendor advisories for updates addressing this issue. In the meantime, mitigating connection churn or avoiding premature pipeline connection closures may reduce the impact.
Io.netty:netty codec redis: Netty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator (CVE-2026-48006)
Description
The Netty RedisArrayAggregator handler leaks pooled direct-memory buffers when a Redis pipeline connection closes prematurely before completing a RESP array aggregate. This occurs because the handler retains child messages in internal state but lacks lifecycle cleanup methods to release these buffers on connection teardown. The leak prevents memory chunks from returning to the JVM-wide direct-memory pool, causing gradual depletion of this shared resource. Repeated connection churn can lead to allocation failures across all Netty channels in the affected process.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48006 describes a resource leak vulnerability in the Netty io.netty:netty-codec-redis component, specifically in the RedisArrayAggregator handler. When a Redis pipeline connection closes before a RESP array aggregate completes, pooled direct-memory buffers are permanently leaked because the handler retains child messages in its 'depths' field but does not implement channel lifecycle cleanup methods such as channelInactive, handlerRemoved, or exceptionCaught to release these buffers. Since these buffers are slices of PooledByteBufAllocator chunks, the leak prevents these chunks from being returned to the JVM-wide direct-memory pool. This leads to a monotonic drain of the shared pool under repeated connection churn, ultimately causing allocation failures on all Netty channels within the process.
Potential Impact
The vulnerability causes a denial of service condition by leaking pooled direct-memory buffers, which depletes the JVM-wide direct-memory pool. This resource exhaustion can lead to allocation failures on all Netty channels in the affected process, potentially disrupting network communications that rely on Netty. There are no known exploits in the wild currently.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Users should monitor vendor advisories for updates addressing this issue. In the meantime, mitigating connection churn or avoiding premature pipeline connection closures may reduce the impact.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6jv9-x5w9-2ccm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-48006"]
- Ecosystems
- ["Maven"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a520efa68715ace4391e4ec
Added to database: 07/11/2026, 09:38:02 UTC
Last enriched: 07/11/2026, 10:14:31 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 51
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.