Netty is a network application framework for development of protocol servers and clients. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, the SpdyHttpDecoder handler in Netty's SPDY-to-HTTP codec allocates a pooled ByteBuf when processing a client-initiated SYN_STREAM frame with FLAG_FIN=0 and stores the partially constructed FullHttpRequest in messageMap; when the remote peer sends RST_STREAM for that stream or the accumulated content exceeds maxContentLength, the decoder removes the entry but does not release the pooled ByteBuf, causing native memory exhaustion. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.
CVE-2026-56745
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (5)
Auto-updated Jul 22, 2026[SpdyHttpDecoder] ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion · Advisory · netty/netty · GitHub
https://github.com/netty/netty/security/advisories/GHSA-jppx-w49h-x2qqnetty-4.2.16.Final
Patch available: netty/netty netty-4.2.16.Final
https://github.com/netty/netty/releases/tag/netty-4.2.16.Finalnetty-4.1.136.Final
Patch available: netty/netty netty-4.1.136.Final
https://github.com/netty/netty/releases/tag/netty-4.1.136.Finalcommit bb2ff68a1fb7 (netty/netty)
Patch available: netty/netty netty-4.1.136.Final (contains commit bb2ff68a1fb7)
https://github.com/netty/netty/commit/bb2ff68a1fb71cb4b0eb9a9e17b66c52aff680c6commit 5b68c61f37aa (netty/netty)
Patch available: netty/netty netty-4.2.16.Final (contains commit 5b68c61f37aa)
https://github.com/netty/netty/commit/5b68c61f37aa4a3045cba624cbea239655c9003bVendor Advisories for CVE-2026-56745(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| io.netty:netty-codec-http | 4.1.0.Final ... 4.1.99.Final (136 versions) | 4.1.136.Final | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 19:35 UTCEG score recompute
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-26 21:08 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 09:57 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 22:55 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 23:09 UTCEG score recompute
- 2026-07-21 21:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-56745?
When was CVE-2026-56745 disclosed?
Is CVE-2026-56745 actively exploited?
What is the CVSS score of CVE-2026-56745?
How do I remediate CVE-2026-56745?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56745
Is Your Infrastructure Affected by CVE-2026-56745?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.