CVE-2026-48617

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw in Node.js Permission Model enforcement allows Bypass via process.report.writeReport() Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
42
EG Risk 42/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

Published

June 18, 2026

Last Modified

August 19, 2026

Advisory Details (2)

Auto-updated Aug 19, 2026
Patch available.
generic

Node.js — Thursday, June 18, 2026 Security Releases

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

HackerOne

http://hackerone.com/reports/3692858

Vendor Advisories for CVE-2026-48617(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs24-main-24.18.0-0.6.hum12026-07-26redhat
redhatnodejs26-main-26.5.0-1.5.hum12026-07-25redhat
redhatnodejs22-main-22.23.1-2.3.hum12026-07-24redhat

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.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-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.16.0+dfsg+~cs24.13.1-2 (38 versions)
  • every version up to 24.17.0+dfsg+~cs24.13.2-1: fixed in 24.17.0+dfsg+~cs24.13.2-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 27× 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 161 total refreshes for this CVE.

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

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

Same vendor

2 shown

redhat:RHSA-2026:45381 · redhat:RHSA-2026:45783

Frequently asked(5)

What is CVE-2026-48617?
CVE-2026-48617 is a high vulnerability published on June 18, 2026. A flaw in Node.js Permission Model enforcement allows Bypass via process.report.writeReport() Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: Node.js 22,…
When was CVE-2026-48617 disclosed?
CVE-2026-48617 was first published on June 18, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48617 actively exploited?
CVE-2026-48617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48617?
CVE-2026-48617 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-48617?
A fix for CVE-2026-48617 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48617 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-48617

Explore →

Is Your Infrastructure Affected by CVE-2026-48617?

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

Book a Demo →Browse All CVEs