RedisArrayAggregator - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/redisarrayaggregator/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 18 Sep 2026 14:05:50 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgResource Exhaustion in RedisArrayAggregatorhttps://feed.craftedsignal.io/briefs/2026-09-redis-array-aggregator-dos/Fri, 18 Sep 2026 14:05:50 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-redis-array-aggregator-dos/A vulnerability in RedisArrayAggregator allows remote attackers to trigger memory exhaustion via a crafted RESP payload that forces eager allocation of array capacity.CVE-2026-93572 is a resource exhaustion vulnerability affecting the RedisArrayAggregator component. The issue stems from the eager allocation of ArrayList capacity based on nested RESP array headers. The implementation checks 'maxElements' and 'maxNestedArrayDepth' independently, failing to account for the cumulative memory impact of nested array allocations. An attacker can send a series of nested RESP array headers, each specifying a large length, which forces the application to create 'new ArrayList<RedisMessage>(length)' for every header. Because the memory is reserved upon receipt of the header before the actual array elements are processed, an attacker can consume massive amounts of system memory with a relatively small input payload, leading to a Denial of Service (DoS) state. This vulnerability highlights the risk of relying on independent limit checks in recursive parsing logic.

Impact

Successful exploitation results in a Denial of Service due to memory exhaustion. The vulnerability allows an attacker to disproportionately consume system memory relative to the size of the malicious input, which can crash the application or destabilize the host system depending on the available heap space and resource constraints.

Recommendation

  1. Audit applications utilizing RedisArrayAggregator to determine if user-controlled input can reach the affected RESP decoding logic.
  2. Implement strict input validation or application-level rate limiting for incoming RESP traffic until a patch is available.
  3. Monitor application memory usage and heap allocation patterns; unusual spikes correlated with high-frequency incoming array headers may indicate exploitation attempts.
]]>lowadvisorydenial-of-servicememory-exhaustionredis