CVE-2026-56847

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-30) is not newer than that change (2026-08-25), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week
6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw in Node.js Permission Model enforcement allows trace_events.createTracing().enable() Writes Trace Logs Outside --allow-fs-write. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects Node.js 22.x, 24.x, and 26.x.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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 (value × EchelonGraph’s weight)
Severity61% × 45%
The EG Score, 6.1 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Aug 25, 2026
Patch available.
Web page

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

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

Vendor Advisories for CVE-2026-56847(5)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs24-main-11.16.0-1.24.18.1.0.1.hum12026-07-30redhat
redhatnodejs26-main-11.17.0-1.26.5.1.1.5.hum12026-07-29redhat
redhatnodejs22-main-10.9.8-1.22.23.2.2.3.hum12026-07-29redhat

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

(6 across 6 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: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.

Data Freshness Timeline

(refreshed 16× in last 7d / 82× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 195 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same CWE

1 shown

CWE-1119

Frequently asked(5)

What is CVE-2026-56847?
CVE-2026-56847 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. A flaw in Node.js Permission Model enforcement allows trace_events.createTracing().enable() Writes Trace Logs Outside --allow-fs-write. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects Node.js 22.x, 24.x,…
When was the CVE record for CVE-2026-56847 published?
The CVE record for CVE-2026-56847 was published on July 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56847 actively exploited?
CVE-2026-56847 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56847?
CVE-2026-56847 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-56847?
A fix for CVE-2026-56847 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56847 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-56847

Explore →

Is Your Infrastructure Affected by CVE-2026-56847?

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

Book a Demo →Browse All CVEs