CVE-2026-48935

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-06-26. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw in Node.js Permission API can cause a file metadata to be modified even on a path that was set as read-only with e.g. --allow-fs-read. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
19
EG Risk 19/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
Severity33% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

References (1)

Vendor Advisories for CVE-2026-48935(12)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs22-main-22.23.1-2.hum12026-07-03redhat
redhatnodejs24-main-24.18.0-0.2.hum12026-07-01redhat
redhatnodejs26-main-26.4.0-1.3.hum12026-06-30redhat
redhatnodejs20-main-20.20.2-1.hum12026-04-21redhat
redhatnodejs25-main-25.9.0-1.1.hum12026-04-10redhat

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

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

Frequently asked(5)

What is CVE-2026-48935?
CVE-2026-48935 is a low vulnerability published on June 26, 2026. A flaw in Node.js Permission API can cause a file metadata to be modified even on a path that was set as read-only with e.g. --allow-fs-read. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
When was CVE-2026-48935 disclosed?
CVE-2026-48935 was first published on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48935 actively exploited?
CVE-2026-48935 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48935?
CVE-2026-48935 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48935?
A fix for CVE-2026-48935 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48935 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-48935

Explore →

Is Your Infrastructure Affected by CVE-2026-48935?

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

Book a Demo →Browse All CVEs