CVE-2026-50011
Undergoing Analysis Undergoing Analysis - In Progress
Memory Exhaustion in Netty via RedisArrayAggregator

Publication date: 2026-06-12

Last updated on: 2026-06-12

Assigner: GitHub, Inc.

Description
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, RedisArrayAggregator pre-allocates ArrayList with initial capacity equal to the RESP array element count declared in an array header. That count is taken from the wire before the corresponding child messages exist. A small malicious header can claim a huge initial capacity. Versions 4.1.135.Final and 4.2.15.Final patch the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-12
Last Modified
2026-06-12
Generated
2026-06-12
AI Q&A
2026-06-12
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
netty netty to 4.2.15.Final|end_excluding=4.1.135.Final (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-50011 is an unbounded pre-allocation vulnerability in the RedisArrayAggregator component of Netty's Redis codec library. The vulnerability occurs because the aggregator pre-allocates an ArrayList with an initial capacity based on the RESP array length declared in the array header, which is read directly from the network before the actual child messages are processed.

A malicious actor can exploit this by sending a RESP array header with an extremely large declared length, causing the aggregator to attempt to allocate a huge amount of memory. This can lead to resource exhaustion and potential denial-of-service (DoS) conditions.

The root cause is the lack of a configurable maximum limit on array header lengths in RedisArrayAggregator, unlike other parts of the code that enforce limits on bulk string lengths.

Impact Analysis

This vulnerability can impact you by causing resource exhaustion on systems running vulnerable versions of Netty. Specifically, it can lead to denial-of-service (DoS) conditions by forcing the application to allocate excessive memory based on maliciously crafted network input.

The attack is network-based, has low complexity, requires no privileges or user interaction, and primarily affects the availability of the affected system or service.

Detection Guidance

This vulnerability can be detected by monitoring network traffic for suspicious Redis RESP array headers that declare unusually large array lengths, which may indicate an attempt to exploit the unbounded pre-allocation in RedisArrayAggregator.

Since the vulnerability involves a malicious RESP array header with a very large declared length, detection can involve capturing and inspecting Redis protocol traffic for abnormal array header sizes.

Commands or tools that can help detect this include using packet capture utilities like tcpdump or Wireshark to filter Redis traffic and analyze RESP array headers.

  • Use tcpdump to capture Redis traffic on the default port 6379: tcpdump -i <interface> port 6379 -w redis_traffic.pcap
  • Open the capture in Wireshark and filter for Redis protocol messages, then inspect array headers for unusually large declared lengths.
  • Alternatively, use Redis protocol parsers or custom scripts to parse logs or traffic and flag RESP array headers with excessively large lengths.
Mitigation Strategies

The immediate mitigation step is to upgrade Netty to a patched version where this vulnerability is fixed.

  • Upgrade to Netty version 4.1.135.Final or later.
  • Upgrade to Netty version 4.2.15.Final or later.

These versions include patches that add limits to the array header length pre-allocation in RedisArrayAggregator, preventing resource exhaustion.

Until an upgrade is possible, consider network-level protections such as rate limiting or filtering suspicious Redis traffic to reduce exposure to malicious RESP array headers.

Compliance Impact

CVE-2026-50011 is a denial-of-service vulnerability caused by unbounded memory allocation in Netty's RedisArrayAggregator. It primarily impacts system availability by enabling resource exhaustion through network-based attacks.

While the vulnerability affects availability, there is no direct information provided about impacts on confidentiality or integrity of data, which are critical factors for compliance with standards like GDPR or HIPAA.

Therefore, based on the available information, this vulnerability could indirectly affect compliance by causing service disruptions, which may impact availability requirements under certain regulations. However, no explicit linkage to compliance violations or data breaches is stated.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-50011. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart