CVE-2026-56818: Netty: RedisArrayAggregator max-elements failure leaves retained partial aggregate state
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: io.netty:netty-codec-redis (Maven) 4.2.16.Final, 4.1.136.Final; netty (openSUSE:Tumbleweed) 4.1.136-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.80-150200.3.48.1.
Low priority for now. Upgrade to io.netty:netty-codec-redis (Maven) 4.2.16.Final, 4.1.136.Final; netty (openSUSE:Tumbleweed) 4.1.136-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.80-150200.3.48.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 7, 2026
- Updated
- Sep 23, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-401
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · GitHub_M
- 6.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| netty | netty | cpe:2.3:a:netty:netty |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
netty netty
- < 4.1.136.Final, >= 4.2.0-Final, < 4.2.16.Finalaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netty nettybefore 4.1.136
- netty netty4.2.0 and later · before 4.2.16
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | netty | from 0 | — |
| Maven | io.netty:netty-codec-redis | from 4.2.0-Final · before 4.2.16.Final | 4.2.16.Final |
| Maven | io.netty:netty-codec-redis | before 4.1.136.Final | 4.1.136.Final |
| openSUSE:Tumbleweed | netty | before 4.1.136-1.1 | 4.1.136-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | netty-tcnative | before 2.0.80-150200.3.48.1 | 2.0.80-150200.3.48.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | netty | before 4.1.136-150200.4.53.1 | 4.1.136-150200.4.53.1 |
Same product
netty: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-47691Netty has Insufficient Bailiwick Validation for NS Records40Plan
- CVE-2026-45674Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records40Plan
- CVE-2019-20445HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-59920Jul 29, 2026 · Netty: STOMP CONNECT Frame Header Injection26Monitor
- ← EarlierCVE-2026-59898Jul 29, 2026 · Netty: WebSockets V07/V08 handshaker missing Connection/Upgrade validation25Monitor
- Later →CVE-2026-73507Aug 13, 2026 · Netty: Denial of Service in XmlFrameDecoder via CPU Exhaustion30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:io.netty:netty-codec-redis | 4.1.136.Final | Package registry (OSV) |
| Maven:io.netty:netty-codec-redis | 4.2.16.Final | Package registry (OSV) |
| opensuse:netty | 4.1.136-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:netty | 4.1.136-150200.4.53.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:netty-tcnative | 2.0.80-150200.3.48.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4800656 days apartNetty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in RedisArrayAggregator34Monitor
- CVE-2026-4805956 days apartNetty HAProxy: Unbalanced Reference Count in Nested PP2_TYPE_SSL TLV Parsing Leads to Memory Exhaustion34Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.