Answer in brief
CVE-2026-44250 records a High severity (CVSS 7.5) vulnerability in Netty: Memory Exhaustion in RedisArrayAggregator due to Deeply Nested Arrays. The current sources do not mark it as known exploited. The current feed maps netty/netty (generic), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps netty/netty (generic), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven), io.netty:netty-codec-redis (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| netty/nettygeneric | >= 4.2.0.Final, < 4.2.15.Final || < 4.1.135.Final | Not reported |
| io.netty:netty-codec-redismaven | >=4.2.0.Final,<=4.2.14.Final | 4.2.15.Final |
| io.netty:netty-codec-redismaven | <=4.1.134.Final | 4.1.135.Final |
| io.netty:netty-codec-redismaven | >=4.2.0.Final <4.2.15.Final | 4.2.15.Final |
| io.netty:netty-codec-redismaven | >=0 <4.1.135.Final | 4.1.135.Final |
Published upstream
Jun 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.