Skip to main content
VulnerabilityPublished Updated

CVE-2026-21715: nodejs node · Incorrect Permissions

Affects nodejs nodeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.3 Low.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.0 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • 4.0 – 19.0
  • >=20.20.1 <=20.20.1
  • >=22.22.1 <=22.22.1
  • >=24.14.0 <=24.14.0
  • >=25.8.1 <=25.8.1
16 affected builds
Fixed in–
npmnodepkg:npm/nodeOther threatsAffected
  • 4.0 – 25.8.1
20 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, avoid running untrusted code with restricted --allow-fs-read permissions relying on fs.realpathSync.native() for security enforcement. Consider using alternative filesystem functions that correctly enforce permission checks or implement additional access controls at the application level. Monitor Node.js security channels for updates regarding patches or official fixes.

Description

A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync.native()` without the required read permission checks, while all comparable filesystem functions correctly enforce them. As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync.native()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories. This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-read` is intentionally restricted.

References

Community reviews

Loading reviews…