CVE-2026-58043

HIGHNVD 8.48.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% 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 — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries. Under --permission, an attacker who is granted access to one path can abuse boundary handling to read from or write to paths outside the intended filesystem allowlist. This vulnerability affects Node.js main, 22.x, 24.x, and 26.x.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

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

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

Patch Availability(11)

Vendor / EcosystemFixed in / 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
redhatnodejs:24-9080020260819113946.rhel92026-08-31redhat
redhatnodejs22-1:22.23.2-1.el10_22026-08-31redhat
redhatnodejs24-1:24.19.0-1.el10_22026-08-31redhat
redhatnodejs:22-9080020260819113937.rhel92026-08-31redhat
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
nodejs22.23.2-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs22.23.2-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs24.18.1-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs24.18.1-r0
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.20.0+dfsg+~cs24.13.3-2 (45 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.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

(6)

Data Freshness Timeline

(refreshed 31× in last 7d / 137× 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 233 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58043?
CVE-2026-58043 is a high vulnerability published on July 30, 2026. A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries. Under --permission, an attacker who is granted access to one path can abuse boundary handling to read from or write to paths outside the intended filesystem allowlist. This…
When was CVE-2026-58043 disclosed?
CVE-2026-58043 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-58043 actively exploited?
CVE-2026-58043 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 95.8% of all scored CVEs.
What is the CVSS score of CVE-2026-58043?
CVE-2026-58043 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-58043?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58043, 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-58043

Explore →

Is Your Infrastructure Affected by CVE-2026-58043?

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