CVE-2026-56847

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Aug 25, 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-56847(4)

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 / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-main-24.18.1-0.1.hum12026-07-30redhat
redhatnodejs26-main-26.5.1-1.5.hum12026-07-29redhat
redhatnodejs22-main-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 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: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.

Additional Vendor Advisories

(1)

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 21× in last 7d / 67× 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-27 20:49 UTCEG score recompute
  2. 2026-08-27 20:49 UTCVendor advisory
  3. 2026-08-27 20:49 UTCGHSA enrichment
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 19:19 UTCEG score recompute
  6. 2026-08-26 19:19 UTCVendor advisory
  7. 2026-08-26 19:19 UTCGHSA enrichment
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 17:56 UTCEG score recompute▲ 2.80
  10. 2026-08-25 17:56 UTCVendor advisory
  11. 2026-08-25 17:56 UTCGHSA enrichment
  12. 2026-08-25 17:56 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 07:43 UTCEG score recompute
  15. 2026-08-24 07:43 UTCVendor advisory
  16. 2026-08-24 07:43 UTCGHSA enrichment
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-21 05:51 UTCEG score recompute
  20. 2026-08-21 05:51 UTCVendor advisory
  21. 2026-08-21 05:51 UTCGHSA enrichment
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-18 03:58 UTCEG score recompute
Show 42 more
  1. 2026-08-18 03:58 UTCVendor advisory
  2. 2026-08-18 03:58 UTCGHSA enrichment
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 02:04 UTCEG score recompute
  7. 2026-08-15 02:04 UTCVendor advisory
  8. 2026-08-15 02:04 UTCGHSA enrichment
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-12 00:12 UTCEG score recompute
  13. 2026-08-12 00:12 UTCVendor advisory
  14. 2026-08-12 00:12 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-08 22:20 UTCEG score recompute
  18. 2026-08-08 22:20 UTCVendor advisory
  19. 2026-08-08 22:20 UTCGHSA enrichment
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-06 13:47 UTCEPSS rescore
  22. 2026-08-05 20:27 UTCEG score recompute
  23. 2026-08-05 20:27 UTCGHSA enrichment
  24. 2026-08-05 19:17 UTCEPSS rescore
  25. 2026-08-04 15:10 UTCEPSS rescore
  26. 2026-08-04 10:39 UTCEPSS rescore
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 18:35 UTCEG score recompute
  29. 2026-08-02 18:35 UTCGHSA enrichment
  30. 2026-08-02 02:27 UTCEPSS rescore
  31. 2026-08-01 04:16 UTCEPSS rescore
  32. 2026-07-30 16:43 UTCEG score recompute
  33. 2026-07-30 16:43 UTCGHSA enrichment
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-30 13:28 UTCEG score recompute
  36. 2026-07-30 13:28 UTCGHSA enrichment
  37. 2026-07-30 12:48 UTCEG score recompute
  38. 2026-07-30 12:48 UTCGHSA enrichment
  39. 2026-07-30 06:37 UTCEG score recompute
  40. 2026-07-30 06:37 UTCGHSA enrichment
  41. 2026-07-30 06:19 UTCEG score recompute
  42. 2026-07-30 06:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56847?
CVE-2026-56847 is a medium vulnerability 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 CVE-2026-56847 disclosed?
CVE-2026-56847 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56847 actively exploited?
CVE-2026-56847 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 94.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56847, 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-56847

Explore →

Is Your Infrastructure Affected by CVE-2026-56847?

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

Start Free Scan →Browse All CVEs