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

高 7.5CVE-2026-48006 · GHSA-6jv9-x5w9-2ccm · 12/06/2026 公開 · 18/09/2026 更新

要点

CVE-2026-48006 は io.netty:netty-codec-redis, netty (netty) に影響する深刻度「高」 (CVSS 7.5) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.74%（全脆弱性の 54.6% より高い）。
対処：4.2.15.Final, 4.1.135.Final, 4.2.15, 4.1.135 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
io.netty:netty-codec-redis Maven	`≥ 4.2.0.Final, < 4.2.15.Final< 4.1.135.Final`	`4.2.15.Final4.1.135.Final`
netty netty	`≥ 4.2.0, < 4.2.15< 4.1.135`	`4.2.154.1.135`

概要

Impact

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.

NVD の説明

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.