CVE-2026-21715: 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...
Low CVSS 3.3
- CVE id
- CVE-2026-21715
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Node.js Runtimes and servers |
<= 20.20.1 >= 22.0.0, <= 22.22.1 >= 24.0.0, <= 24.14.0 >= 25.0.0, <= 25.8.1 |
after 20.20.1, 22.22.1, 24.14.0, 25.8.1 |
How to fix it
Upgrade Node.js to a release newer than the last affected update of the line you run (20.20.1, 22.22.1, 24.14.0, 25.8.1).
node --version
- Install the patched Node.js release of your major line (nvm install, or the node image tag) everywhere the app runs and builds.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.