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

CAO 7.5CVE-2026-48006 · GHSA-6jv9-x5w9-2ccm · Công bố 12/06/2026 · cập nhật 18/09/2026

Tóm tắt nhanh

CVE-2026-48006 là lỗ hổng mức CAO (CVSS 7.5) ảnh hưởng io.netty:netty-codec-redis, netty (netty).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.74%, cao hơn 54.6% các lỗ hổng khác.
Cách xử lý: cập nhật lên 4.2.15.Final, 4.1.135.Final, 4.2.15, 4.1.135 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
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`

Mô tả

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.

Mô tả của 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.