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.
CVE-2026-56848
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.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- 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 computedSeverity75% × 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, 2026Node.js — Wednesday, July 29, 2026 Security Releases
https://nodejs.org/en/blog/vulnerability/july-2026-security-releasesVendor 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.
- RHSA-2026:64817Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs22 security update
- RHSA-2026:62416Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security update
- RHSA-2026:61383Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security update
- GHSA-679w-638g-xf9hGitHub Security AdvisoriesHigh
A flaw in Node.js HTTP/2 handling allows `nghttp2_session_mem_send()` to be called re-entrantly...
Patch Availability(8)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs22-1:22.23.2-1.el10_0 | 2026-09-08 | redhat |
| redhat | nodejs:22-9060020260901085634.rhel9 | 2026-09-02 | redhat |
| redhat | nodejs:24-8100020260819113942.6d880403 | 2026-09-02 | redhat |
| redhat | nodejs:22-8100020260819113925.6d880403 | 2026-09-01 | redhat |
| redhat | nodejs:22-9080020260819113937.rhel9 | 2026-08-31 | redhat |
| redhat | nodejs:24-9080020260819113946.rhel9 | 2026-08-31 | redhat |
| redhat | nodejs22-1:22.23.2-1.el10_2 | 2026-08-31 | redhat |
| redhat | nodejs24-1:24.19.0-1.el10_2 | 2026-08-31 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 22.23.2-r0 | — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 22.23.2-r0 | — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 24.18.1-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 24.18.1-r0 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 18.13.0+dfsg1-1 ... 24.20.0+dfsg+~cs24.13.3-2 (90 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 20.19.2+dfsg-1 ... 24.20.0+dfsg+~cs24.13.3-2 (45 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 20.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)
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.
- Red HatRHSA-2026:61376IMPORTANT2026-08-04
RHSA-2026:61376 — Important
- Red HatRHSA-2026:61377IMPORTANT2026-08-04
RHSA-2026:61377 — Important
- Red HatRHSA-2026:61386IMPORTANT2026-08-04
RHSA-2026:61386 — Important
- Red HatRHSA-2026:62219IMPORTANT2026-08-04
RHSA-2026:62219 — Important
- Red HatRHSA-2026:62583IMPORTANT2026-08-04
RHSA-2026:62583 — Important
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.
- 2026-09-19 07:58 UTCEG score recompute
- 2026-09-19 07:58 UTCVendor advisory
- 2026-09-19 07:58 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:23 UTCVendor advisory
- 2026-09-18 18:23 UTCGHSA enrichment
- 2026-09-18 05:12 UTCEG score recompute
- 2026-09-18 05:12 UTCVendor advisory
- 2026-09-18 05:12 UTCGHSA enrichment
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 16:14 UTCVendor advisory
- 2026-09-17 16:14 UTCGHSA enrichment
- 2026-09-17 01:11 UTCEG score recompute
- 2026-09-17 01:11 UTCVendor advisory
- 2026-09-17 01:11 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:45 UTCEG score recompute
- 2026-09-16 05:45 UTCVendor advisory
- 2026-09-16 05:45 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 16:48 UTCEG score recompute
- 2026-09-15 16:48 UTCVendor advisory
- 2026-09-15 16:48 UTCGHSA enrichment
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-15 01:40 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-15 01:40 UTCGHSA enrichment
- 2026-09-14 07:42 UTCVendor advisory
- 2026-09-14 07:42 UTCGHSA enrichment
- 2026-09-13 18:44 UTCEG score recompute
- 2026-09-13 18:44 UTCVendor advisory
- 2026-09-13 18:44 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 05:45 UTCVendor advisory
- 2026-09-13 05:45 UTCGHSA enrichment
- 2026-09-12 16:48 UTCEG score recompute
- 2026-09-12 16:48 UTCVendor advisory
- 2026-09-12 16:48 UTCGHSA enrichment
- 2026-09-12 03:50 UTCEG score recompute
- 2026-09-12 03:50 UTCVendor advisory
- 2026-09-12 03:50 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:52 UTCEG score recompute
- 2026-09-11 14:52 UTCVendor advisory
- 2026-09-11 14:52 UTCGHSA enrichment
- 2026-09-10 21:59 UTCEG score recompute
- 2026-09-10 21:59 UTCVendor advisory
- 2026-09-10 21:59 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 08:48 UTCVendor advisory
- 2026-09-10 08:48 UTCGHSA enrichment
- 2026-09-09 19:34 UTCVendor advisory
- 2026-09-09 19:34 UTCGHSA enrichment
- 2026-09-09 06:36 UTCEG score recompute
- 2026-09-09 06:36 UTCVendor advisory
- 2026-09-09 06:36 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 18:34 UTCEG score recompute
- 2026-09-07 18:34 UTCVendor advisory
- 2026-09-07 18:34 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 20:31 UTCEG score recompute
- 2026-09-06 20:31 UTCVendor advisory
- 2026-09-06 20:31 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 07:30 UTCVendor advisory
- 2026-09-06 07:30 UTCGHSA enrichment
- 2026-09-05 18:32 UTCEG score recompute
- 2026-09-05 18:32 UTCVendor advisory
- 2026-09-05 18:32 UTCGHSA enrichment
- 2026-09-05 04:09 UTCEG score recompute
- 2026-09-05 04:09 UTCVendor advisory
- 2026-09-05 04:09 UTCGHSA enrichment
- 2026-09-04 10:08 UTCEG score recompute
- 2026-09-04 10:08 UTCVendor advisory
- 2026-09-04 10:08 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 17:15 UTCVendor advisory
- 2026-09-03 17:15 UTCGHSA enrichment
- 2026-09-03 07:29 UTCEG score recompute
- 2026-09-03 07:29 UTCVendor advisory
- 2026-09-03 07:29 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 20:49 UTCEG score recompute
- 2026-09-01 20:49 UTCVendor advisory
- 2026-09-01 20:49 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 23:01 UTCGHSA enrichment
- 2026-08-30 23:41 UTCEG score recompute
- 2026-08-30 23:41 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 10:44 UTCEG score recompute
- 2026-08-30 10:44 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:46 UTCEG score recompute
- 2026-08-29 21:46 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 02:25 UTCEG score recompute
- 2026-08-28 02:25 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-56848?
When was CVE-2026-56848 disclosed?
Is CVE-2026-56848 actively exploited?
What is the CVSS score of CVE-2026-56848?
How do I remediate CVE-2026-56848?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56848
Is Your Infrastructure Affected by CVE-2026-56848?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.