CVE-2026-21716

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.

Published: 2026-03-30 Last update: 2026-04-01 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-21716 is rated Low Risk (15.2/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.16%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-21716

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.00% 0.16% +0.15%
2 2026-03-31 — 0.00% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-21716

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.0 LOW
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 [email protected]

Weakness enumeration for CVE-2026-21716

OS Trackers for CVE-2026-21716

vendor priority summary link
alpine — CVE-2026-21716: 1 source package rows (nodejs); 4 state rows across 4 repos (3.21-main, 3.22-main, 3.23-main, edge-main); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2026-21716
debian unimportant CVE-2026-21716 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-21716
redhat low — https://access.redhat.com/security/cve/CVE-2026-21716
suse medium CVE-2026-21716 severity moderate: SUSE including 66 source package names (corepack24-24.14.1-1.1, corepack24-24.14.1-160000.1.1, …), 137 product×package rows across 20 product lines (SUSE Liberty Linux 8, SUSE Liberty Linux 9, … (20 product lines)): Known Not Affected 79, Fixed 53, First Fixed 5. https://www.suse.com/security/cve/CVE-2026-21716/
ubuntu medium CVE-2026-21716 medium priority: Ubuntu including 1 source packages (nodejs), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 7, released 1. https://ubuntu.com/security/CVE-2026-21716

Affected software / configurations for CVE-2026-21716

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-21716

cvelogic Threat Intelligence