Answer in brief
CVE-2026-56818 records a Medium severity vulnerability in Netty: RedisArrayAggregator max-elements failure leaves retained partial aggregate state. 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). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-56818 records a Medium severity vulnerability in Netty: RedisArrayAggregator max-elements failure leaves retained partial aggregate state. 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). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| netty/nettygeneric | < 4.1.136.Final || >= 4.2.0-Final, < 4.2.16.Final | Not reported |
| io.netty:netty-codec-redismaven | <4.1.136.Final | 4.1.136.Final |
| io.netty:netty-codec-redismaven | >=4.2.0-Final,<4.2.16.Final | 4.2.16.Final |
Published upstream
Aug 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 7, 2026
Netty is an asynchronous, event-driven network application framework. Prior to 4.1.136.Final and 4.2.16.Final, the RedisArrayAggregator Redis codec clears retained partial aggregate state when the maxNestedArrayDepth limit is exceeded, but it does not clear the same state when the sibling maxElements limit is exceeded. A peer can start a valid RESP array, send a bulk string child, then send a nested array header longer than the configured maxElements. Netty throws a decoder exception in decodeRedisArrayHeader, but the existing partial aggregate remains retained in the handler. If the application leaves the channel alive after the exception, later messages are still consumed into the pre-error aggregate, allowing an unauthenticated peer to keep attacker-controlled aggregate state alive across a security-limit exception and pin retained pooled buffers. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| netty/nettygeneric | < 4.1.136.Final || >= 4.2.0-Final, < 4.2.16.Final | Not reported |
| io.netty:netty-codec-redismaven | <4.1.136.Final | 4.1.136.Final |
| io.netty:netty-codec-redismaven | >=4.2.0-Final,<4.2.16.Final | 4.2.16.Final |
Published upstream
Aug 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 7, 2026
Netty is an asynchronous, event-driven network application framework. Prior to 4.1.136.Final and 4.2.16.Final, the RedisArrayAggregator Redis codec clears retained partial aggregate state when the maxNestedArrayDepth limit is exceeded, but it does not clear the same state when the sibling maxElements limit is exceeded. A peer can start a valid RESP array, send a bulk string child, then send a nested array header longer than the configured maxElements. Netty throws a decoder exception in decodeRedisArrayHeader, but the existing partial aggregate remains retained in the handler. If the application leaves the channel alive after the exception, later messages are still consumed into the pre-error aggregate, allowing an unauthenticated peer to keep attacker-controlled aggregate state alive across a security-limit exception and pin retained pooled buffers. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.
Quoted source text, attributed separately from HOL analysis.