CVE-2026-44250: Netty: Memory Exhaustion in RedisArrayAggregator due to Deeply Nested Arrays

Published Jun 8, 2026
·
Updated

Summary An attacker can cause DoS by sending a crafted Redis payload with deeply nested arrays. This forces the server to allocate a massive number of state objects and collections, leading to memory exhaustion and an OutOfMemoryError.

Details io.netty.handler.codec.redis.RedisArrayAggregator aggregates RedisMessage parts into ArrayRedisMessage. It uses a Deque<AggregateState> to keep track of nested arrays. However, it does not limit the maximum depth of nested arrays. When an attacker sends a continuous stream of nested array headers (e.g., 1\r\n1\r\n1\r\n...), RedisArrayAggregator pushes a new AggregateState onto the stack and allocates a new ArrayList for each header. Because there is no depth limit, an attacker can send millions of such headers. This consumes a massive amount of heap memory for the AggregateState instances and their backing ArrayLists, eventually resulting in an OutOfMemoryError.

Impact Denial of Service due to memory exhaustion. Any application using Netty's RedisArrayAggregator to handle untrusted Redis traffic is vulnerable.

Other sources

Netty is a network application framework for development of protocol servers and clients. In netty-codec-redis prior to versions 4.1.135.Final and 4.2.15.Final, an attacker can cause DoS by sending a crafted Redis payload with deeply nested arrays. This forces the server to allocate a massive number of state objects and collections, leading to memory exhaustion and an OutOfMemoryError. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

MITRE

Affected Software

5 affected componentsFixes available
maven/io.netty:netty-codec-redis<=4.1.134.Final
4.1.135.Final
maven/io.netty:netty-codec-redis>=4.2.0.Final<=4.2.14.Final
4.2.15.Final
Netty Netty<4.1.135
Netty Netty>=4.2.0<4.2.15
IBM Netezza Software<=11.3.0.3-IF2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.netty:netty-codec-redis to a version that resolves this vulnerability.

    Fixed in 4.1.135.Final
  2. Upgrade

    Upgrade maven/io.netty:netty-codec-redis to a version that resolves this vulnerability.

    Fixed in 4.2.15.Final
  3. Upgrade

    Upgrade netty-codec-redis/RedisArrayAggregator to a version that resolves this vulnerability.

    Fixed in 4.1.135.Final
  4. Upgrade

    Upgrade netty-codec-redis/RedisArrayAggregator to a version that resolves this vulnerability.

    Fixed in 4.2.15.Final

Event History

Jun 8, 2026
Advisory Published
via GitHub·07:01 PM
Data Sourced
via GitHub·07:01 PM
DescriptionSeverityWeaknessAffected Software
Jun 11, 2026
CVE Published
via MITRE·08:49 PM
Data Sourced
via MITRE·08:49 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·10:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
Affected Software
Aug 20, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-44250?

CVE-2026-44250 has a high severity rating of 7.5.

2

What type of attack can exploit CVE-2026-44250?

CVE-2026-44250 can be exploited to launch a denial of service (DoS) attack.

3

What software components are affected by CVE-2026-44250?

CVE-2026-44250 affects the maven/io.netty:netty-codec-redis library.

4

How can I mitigate CVE-2026-44250?

To mitigate CVE-2026-44250, you should update to the latest versions of the netty-codec-redis library.

5

What is the impact of CVE-2026-44250 on a system?

CVE-2026-44250 can lead to memory exhaustion, causing an OutOfMemoryError on the server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203