An incomplete fix for CVE-2024-36137 leaves FileHandle.chmod() and FileHandle.chown() in the promises API without the required permission checks, while their callback-based equivalents (fs.fchmod(), fs.fchown()) were correctly patched.
As a result, code running under --permission with restricted --allow-fs-write can still use promise-based FileHandle methods to modify file permissions and ownership on already-open file descriptors, bypassing the intended write restrictions.
This vulnerability affects 20.x, 22.x, 24.x, and 25.x processes using the Permission Model where --allow-fs-write is intentionally restricted.
CVE-2026-21716
LOWPre-NVD 3.33.3—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-03-30. the CNA's CVSS baseline 3.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cna:hackerone, ghsa
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 0
A fix is available — apply it.
- CVSS v3
- 3.3
- EG Score
- 3.3(medium)
- EG Risk
- 15(Track)EG Risk 15/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 computedSeverity33% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
March 30, 2026
Last Modified
June 17, 2026
References (1)
Vendor Advisories for CVE-2026-21716(8)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-21716Microsoft Security Response Center (MSRC)Low
An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while their callback-based equivalents (`fs.fchmod()`, `fs.fchown()`) were correctly patched. As a result, code running under `--permission` with restricted `--allow-fs-write` can still use promise-based `FileHandle` methods to modify file permissions and ownership on already-open file descriptors, bypassing the intended write restrictions. This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-write` is intentionally restricted.
- RHSA-2026:7670Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security update
- RHSA-2026:7675Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs24 security update
- RHSA-2026:7387Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:7386Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:7350Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security update
- RHSA-2026:6431Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:6402Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(7)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs24-1:24.14.1-2.el10_1 | 2026-04-13 | redhat |
| redhat | nodejs:24-8100020260408131901.6d880403 | 2026-04-13 | redhat |
| redhat | nodejs22-main-22.22.0-1.3.hum1 | 2026-04-10 | redhat |
| redhat | nodejs20-main-20.20.0-7.1.hum1 | 2026-04-10 | redhat |
| redhat | nodejs:24-9070020260402152654.rhel9 | 2026-04-09 | redhat |
| redhat | nodejs25-main-25.9.0-1.hum1 | 2026-04-02 | redhat |
| redhat | nodejs24-main-24.14.1-4.hum1 | 2026-04-01 | redhat |
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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCVendor advisory
- 2026-07-27 12:50 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p90HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p95HIGH
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-21716?
CVE-2026-21716 is a low vulnerability published on March 30, 2026. An incomplete fix for CVE-2024-36137 leaves FileHandle.chmod() and FileHandle.chown() in the promises API without the required permission checks, while their callback-based equivalents (fs.fchmod(), fs.fchown()) were correctly patched. As a result, code running under --permission with restricted…
When was CVE-2026-21716 disclosed?
CVE-2026-21716 was first published in the National Vulnerability Database on March 30, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21716 actively exploited?
CVE-2026-21716 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-21716?
CVE-2026-21716 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-21716?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21716, 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
Explore the affected products and dependency analysis for CVE-2026-21716
Is Your Infrastructure Affected by CVE-2026-21716?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.