CVE-2026-56745

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 30, 2026

Advisory Details (5)

Auto-updated Jul 22, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

[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-x2qq
github_release Patch Available

netty-4.2.16.Final

Patch available: netty/netty netty-4.2.16.Final

https://github.com/netty/netty/releases/tag/netty-4.2.16.Final
github_release Patch Available

netty-4.1.136.Final

Patch available: netty/netty netty-4.1.136.Final

https://github.com/netty/netty/releases/tag/netty-4.1.136.Final
github_commit Patch Available

commit bb2ff68a1fb7 (netty/netty)

Patch available: netty/netty netty-4.1.136.Final (contains commit bb2ff68a1fb7)

https://github.com/netty/netty/commit/bb2ff68a1fb71cb4b0eb9a9e17b66c52aff680c6
github_commit Patch Available

commit 5b68c61f37aa (netty/netty)

Patch available: netty/netty netty-4.2.16.Final (contains commit 5b68c61f37aa)

https://github.com/netty/netty/commit/5b68c61f37aa4a3045cba624cbea239655c9003b

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-codec-http2026-09-10redhat
redhatrhoai/odh-trustyai-service-rhel9:17881986812026-09-08redhat
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-codec-http4.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 18× in last 7d / 91× 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.

Showing the most recent 100 of 168 total refreshes for this CVE.

  1. 2026-09-11 20:30 UTCEG score recompute
  2. 2026-09-11 20:30 UTCVendor advisory
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 08:52 UTCEG score recompute
  5. 2026-09-11 08:52 UTCVendor advisory
  6. 2026-09-10 09:35 UTCEPSS rescore
  7. 2026-09-09 11:10 UTCEG score recompute
  8. 2026-09-09 11:10 UTCVendor advisory
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 22:27 UTCEG score recompute
  11. 2026-09-07 22:27 UTCVendor advisory
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 10:39 UTCVendor advisory
  15. 2026-09-05 19:50 UTCEG score recompute
  16. 2026-09-05 19:50 UTCVendor advisory
  17. 2026-09-05 08:24 UTCEG score recompute
  18. 2026-09-05 08:24 UTCVendor advisory
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-02 00:55 UTCEG score recompute
  22. 2026-09-02 00:55 UTCVendor advisory
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-31 00:44 UTCEG score recompute
Show 75 more
  1. 2026-08-31 00:44 UTCVendor advisory
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 13:32 UTCVendor advisory
  4. 2026-08-30 02:09 UTCEG score recompute
  5. 2026-08-30 02:09 UTCVendor advisory
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-27 22:23 UTCEG score recompute
  9. 2026-08-27 22:23 UTCVendor advisory
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 11:12 UTCVendor advisory
  12. 2026-08-26 23:06 UTCEG score recompute
  13. 2026-08-26 23:06 UTCVendor advisory
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-26 11:54 UTCVendor advisory
  16. 2026-08-26 00:44 UTCEG score recompute
  17. 2026-08-26 00:44 UTCVendor advisory
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-25 13:13 UTCVendor advisory
  20. 2026-08-25 02:02 UTCVendor advisory
  21. 2026-08-24 14:52 UTCEG score recompute
  22. 2026-08-24 14:52 UTCVendor advisory
  23. 2026-08-24 03:41 UTCVendor advisory
  24. 2026-08-23 15:56 UTCVendor advisory
  25. 2026-08-23 04:46 UTCEG score recompute
  26. 2026-08-23 04:46 UTCVendor advisory
  27. 2026-08-23 00:19 UTCEPSS rescore
  28. 2026-08-22 17:35 UTCVendor advisory
  29. 2026-08-22 06:24 UTCEG score recompute
  30. 2026-08-22 06:24 UTCVendor advisory
  31. 2026-08-21 23:49 UTCEPSS rescore
  32. 2026-08-21 19:13 UTCVendor advisory
  33. 2026-08-21 08:02 UTCEG score recompute
  34. 2026-08-21 08:02 UTCVendor advisory
  35. 2026-08-20 22:55 UTCEPSS rescore
  36. 2026-08-20 20:51 UTCVendor advisory
  37. 2026-08-20 09:40 UTCVendor advisory
  38. 2026-08-19 22:28 UTCEG score recompute
  39. 2026-08-19 22:28 UTCVendor advisory
  40. 2026-08-19 17:04 UTCEPSS rescore
  41. 2026-08-19 07:41 UTCVendor advisory
  42. 2026-08-18 20:30 UTCEG score recompute
  43. 2026-08-18 20:30 UTCVendor advisory
  44. 2026-08-18 13:48 UTCEPSS rescore
  45. 2026-08-18 09:19 UTCVendor advisory
  46. 2026-08-17 20:50 UTCEG score recompute
  47. 2026-08-17 20:50 UTCVendor advisory
  48. 2026-08-17 13:47 UTCEPSS rescore
  49. 2026-08-17 08:46 UTCVendor advisory
  50. 2026-08-16 21:36 UTCEG score recompute
  51. 2026-08-16 21:36 UTCVendor advisory
  52. 2026-08-16 14:56 UTCEPSS rescore
  53. 2026-08-16 10:24 UTCEG score recompute
  54. 2026-08-16 10:24 UTCVendor advisory
  55. 2026-08-16 02:14 UTCEPSS rescore
  56. 2026-08-15 23:14 UTCVendor advisory
  57. 2026-08-15 12:03 UTCEG score recompute
  58. 2026-08-15 12:03 UTCVendor advisory
  59. 2026-08-15 01:30 UTCEPSS rescore
  60. 2026-08-15 00:52 UTCVendor advisory
  61. 2026-08-14 13:41 UTCVendor advisory
  62. 2026-08-14 02:31 UTCEG score recompute
  63. 2026-08-14 02:31 UTCVendor advisory
  64. 2026-08-13 22:00 UTCEPSS rescore
  65. 2026-08-13 15:19 UTCVendor advisory
  66. 2026-08-13 04:07 UTCVendor advisory
  67. 2026-08-12 16:57 UTCEG score recompute
  68. 2026-08-12 16:57 UTCVendor advisory
  69. 2026-08-12 13:51 UTCEPSS rescore
  70. 2026-08-12 05:46 UTCVendor advisory
  71. 2026-08-11 18:35 UTCEG score recompute
  72. 2026-08-11 18:35 UTCVendor advisory
  73. 2026-08-11 07:24 UTCEG score recompute
  74. 2026-08-11 07:24 UTCVendor advisory
  75. 2026-08-11 00:00 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-56745?
CVE-2026-56745 is a high vulnerability published on July 21, 2026. 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…
When was CVE-2026-56745 disclosed?
CVE-2026-56745 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56745 actively exploited?
CVE-2026-56745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.7% of all scored CVEs.
What is the CVSS score of CVE-2026-56745?
CVE-2026-56745 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56745?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56745, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56745

Explore →

Is Your Infrastructure Affected by CVE-2026-56745?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.