Answer in brief
CVE-2026-48006 records a High severity (CVSS 7.5) vulnerability in Netty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator. The current sources do not mark it as known exploited. The current feed maps netty/netty (generic), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps netty/netty (generic), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| netty/nettygeneric | >= 4.2.0.Final, < 4.2.15.Final || < 4.1.135.Final | Not reported |
| io.netty:netty-codec-redismaven | >=4.2.0.Final,<=4.2.14.Final | 4.2.15.Final |
| io.netty:netty-codec-redismaven | <=4.1.134.Final | 4.1.135.Final |
| io.netty:netty-codec-redismaven | >=4.2.0.Final <4.2.15.Final | 4.2.15.Final |
| io.netty:netty-codec-redismaven | >=0 <4.1.135.Final | 4.1.135.Final |
Published upstream
Jun 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 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 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.
Quoted source text, attributed separately from HOL analysis.