CVE-2026-56848

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH 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 — 3 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: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
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

August 4, 2026

Last Modified

August 4, 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

Vendor Advisories for CVE-2026-56848(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.2-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.2-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.18.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.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.18.0+dfsg+~cs24.13.2-1 (87 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (42 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 66× 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.

  1. 2026-08-21 01:36 UTCEG score recompute
  2. 2026-08-21 01:36 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 12:38 UTCGHSA enrichment
  5. 2026-08-19 23:41 UTCEG score recompute
  6. 2026-08-19 23:41 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:43 UTCGHSA enrichment
  9. 2026-08-18 21:43 UTCEG score recompute
  10. 2026-08-18 21:43 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 08:39 UTCGHSA enrichment
  13. 2026-08-17 19:34 UTCEG score recompute
  14. 2026-08-17 19:34 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 04:59 UTCGHSA enrichment
  17. 2026-08-16 16:01 UTCEG score recompute
  18. 2026-08-16 16:01 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 03:04 UTCEG score recompute
  21. 2026-08-16 03:04 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 14:07 UTCEG score recompute
  24. 2026-08-15 14:07 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 41 more
  1. 2026-08-15 01:09 UTCGHSA enrichment
  2. 2026-08-14 12:11 UTCGHSA enrichment
  3. 2026-08-13 23:14 UTCEG score recompute
  4. 2026-08-13 23:14 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 10:17 UTCGHSA enrichment
  7. 2026-08-12 21:19 UTCEG score recompute
  8. 2026-08-12 21:19 UTCGHSA enrichment
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 08:22 UTCGHSA enrichment
  11. 2026-08-11 19:25 UTCEG score recompute
  12. 2026-08-11 19:25 UTCGHSA enrichment
  13. 2026-08-11 06:27 UTCEG score recompute
  14. 2026-08-11 06:27 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 17:30 UTCGHSA enrichment
  17. 2026-08-10 04:33 UTCGHSA enrichment
  18. 2026-08-09 15:35 UTCEG score recompute
  19. 2026-08-09 15:35 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 02:38 UTCEG score recompute
  22. 2026-08-09 02:38 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 13:41 UTCGHSA enrichment
  25. 2026-08-08 00:43 UTCEG score recompute
  26. 2026-08-08 00:43 UTCGHSA enrichment
  27. 2026-08-07 11:45 UTCGHSA enrichment
  28. 2026-08-06 22:47 UTCEG score recompute
  29. 2026-08-06 22:47 UTCGHSA enrichment
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-06 09:18 UTCGHSA enrichment
  32. 2026-08-05 20:21 UTCEG score recompute
  33. 2026-08-05 20:21 UTCGHSA enrichment
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 07:24 UTCEG score recompute
  36. 2026-08-05 07:24 UTCGHSA enrichment
  37. 2026-08-04 18:25 UTCEG score recompute
  38. 2026-08-04 17:59 UTCEG score recompute
  39. 2026-08-04 17:23 UTCEG score recompute
  40. 2026-08-04 16:27 UTCEG score recompute
  41. 2026-08-04 16:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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. 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 1% probability of exploitation in the next 30 days, which ranks it in the top 52.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.

Start Free Scan →Browse All CVEs