Node.js is vulnerable to Permission Model file-name disclosure via recursive fs.watch
cve-program · CVE-2026-123829
PublishedA Permission Model bypass in Node.js recursive file watching discloses the names of files and directories the process is not permitted to read. On macOS and Windows, fs.watch() and fs.promises.watch() in recursive mode are backed by the native libuv watcher: FSEventWrap::Start checks kFileSystemRead only once, on the watched root, and FSEventWrap::OnEvent then forwards every filename libuv reports (relative paths at any depth) to the JavaScript callback without checking that each path is covered by the read grant. Code running under --permission with an exact read grant on a directory can therefore learn names such as sub/secret.txt even though readdir on that subdirectory is denied. The flaw exposes names and timing metadata, not file contents, and requires macOS or Windows plus files created under the watched directory by another actor. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-123829 · CVE overview and exploitation status
cve-program · CVE-2026-123829
Related changes
Linked by CVE identifier- Node.js is vulnerable to Permission Model file-name disclosure via recursive fs.watch · Newly collected advisory · 11 Nov 2026
- Wednesday, November 11, 2026 Security Releases · Security advisory · 11 Nov 2026