A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered `fs.realpathSync.native()`. As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
Fix
Microsoft's update · Low
- Release Notes — azl3 nodejs 24.21.0-1 on Azure Linux 3.0 · build 24.22.1-0
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-28.
Public exploits 2
- CompleTetech-Security/node-cve-2026-106073-check PoC on GitHub
- completetech-security/node-cve-2026-106073-check PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 16:15
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-23 19:42
- StatusReceived → PublishedNVD modified 2026-10-23 16:15
- First seenCVSS 3.3NVD modified 2026-10-23 17:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.