CVE-2026-44890: Netty has Unbounded Direct Memory Consumption in its RedisDecoder
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: netty 4.1.135; netty 4.2.15 upper bounds of the CVE record's affected ranges
- Later advisories still cover the fixes above and name higher ones: netty-codec-redis 4.2.16.Final (CVE-2026-56818) OSV advisories
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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 crafted Redis payloads across multiple connections without `\r\n`. This exhausts the server's direct memory pool (OutOfDirectMemoryError), preventing legitimate connections from being processed. Versions 4.1.135.Final and 4.2.15.Final patch the issue.
- weakness
- CWE-400: Uncontrolled Resource Consumption
- affected
- netty
- published ranges
- netty < 4.1.135; netty >= 4.2.0 < 4.2.15
- first unaffected version, by branch
- netty 4.1.135; netty 4.2.15
- fixed by package (from OSV advisories)
- io.netty:netty-codec-redis (Maven): 4.1.135.Final; 4.2.15.Final GHSA-6ghj-frrj-jjj3
- later fixes (from OSV advisories)
- netty-codec-redis 4.1.135.Final is inside a range CVE-2026-56818 (GHSA-p9jm-q85p-7mcp) lists as affected. That advisory is fixed in 4.1.136.Final.netty-codec-redis 4.2.15.Final is inside a range CVE-2026-56818 (GHSA-p9jm-q85p-7mcp) lists as affected. That advisory is fixed in 4.2.16.Final.
- severity
- 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- assigned by
- GitHub_M
- published
- 2026-06-11
check us github.com github.com github.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 12 Jun 2026 | 0.00038 | |
| 15 Jun 2026 | 0.00609 | scoring model v2026.06.15 |
| 23 Jun 2026 | 0.00335 | |
| 30 Jun 2026 | 0.00371 | |
| 11 Jul 2026 | 0.0038 | |
| 22 Jul 2026 | 0.00389 | |
| 6 Aug 2026 | 0.00449 | |
| 13 Aug 2026 | 0.00461 | |
| 28 Sep 2026 | 0.00849 |
9 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: netty 4.1.135; netty 4.2.15. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-44890', '2026-10-31T23:59:59.999999Z', now());