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.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
Patch available.
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(4)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / 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
redhatnodejs24-1:24.19.0-1.el10_22026-08-31redhat
redhatnodejs:24-9080020260819113946.rhel92026-08-31redhat
redhatnodejs:22-9080020260819113937.rhel92026-08-31redhat
redhatnodejs22-1:22.23.2-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 rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.2-r0: fixed in 22.23.2-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.2-r0: fixed in 22.23.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.18.1-r0: fixed in 24.18.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.18.1-r0: fixed in 24.18.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 18.20.4+dfsg-1~deb12u2 (22 versions)
  • every version up to 18.20.4+dfsg-1~deb12u3: fixed in 18.20.4+dfsg-1~deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
  • every version up to 20.19.2+dfsg-1+deb13u3: fixed in 20.19.2+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions)
  • every version up to 24.19.0+dfsg+~cs24.13.3-1: fixed in 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)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 26× in last 7d / 128× 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 246 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + 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 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.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56848?
CVE-2026-56848 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56848?
A fix for CVE-2026-56848 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56848 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs