CVE-2026-56848

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated 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: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw in Node.js HTTP/2 handling allows nghttp2_session_mem_send() to be called re-entrantly while nghttp2_session_mem_recv() is executing, resulting in a heap-use-after-free. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

August 4, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

Node.js — Wednesday, July 29, 2026 Security Releases

https://nodejs.org/en/blog/vulnerability/july-2026-security-releases

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs22-1:22.23.2-1.el10_02026-09-08redhat
redhatnodejs:22-9060020260901085634.rhel92026-09-02redhat
redhatnodejs:24-8100020260819113942.6d8804032026-09-02redhat
redhatnodejs:22-8100020260819113925.6d8804032026-09-01redhat
redhatnodejs:22-9080020260819113937.rhel92026-08-31redhat
redhatnodejs:24-9080020260819113946.rhel92026-08-31redhat
redhatnodejs22-1:22.23.2-1.el10_22026-08-31redhat
redhatnodejs24-1:24.19.0-1.el10_22026-08-31redhat

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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
nodejs22.23.2-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs22.23.2-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs24.18.1-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs24.18.1-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nodejs18.13.0+dfsg1-1 ... 24.20.0+dfsg+~cs24.13.3-2 (90 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.20.0+dfsg+~cs24.13.3-2 (45 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions)24.19.0+dfsg+~cs24.13.3-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 37× in last 7d / 125× 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 187 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-56848?
CVE-2026-56848 is a high vulnerability published on August 4, 2026. A flaw in Node.js HTTP/2 handling allows nghttp2sessionmemsend() to be called re-entrantly while nghttp2sessionmemrecv() is executing, resulting in a heap-use-after-free. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
When was CVE-2026-56848 disclosed?
CVE-2026-56848 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56848 actively exploited?
CVE-2026-56848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 58.8% of all scored CVEs.
What is the CVSS score of CVE-2026-56848?
CVE-2026-56848 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56848?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56848, 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-56848

Explore →

Is Your Infrastructure Affected by CVE-2026-56848?

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