CVSS 3.0
2.5 lowCVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:NCVE-2026-123829 Node.js is vulnerable to Permission Model file-name disclosure via recursive fs.watch
Low (2.5) in nodejs node. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
On this page
A 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.
Severity
- EPSS
- 0.1% estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- openjs (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123829 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123829?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123829?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123829 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123829)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123829"><img src="https://cve.bz/cve/badge/CVE-2026-123829.svg" alt="CVE-2026-123829"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nodejs node | from 0.0.0 before 22.23.5 |
| nodejs node | from 23.0.0 before 24.22.3 |
| nodejs node | from 25.0.0 before 26.13.1 |
Fix and patched versions
- Red Hat, Alpine, Alpaquita, BellSoft Hardened Containers: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | nodejs | no fix listed | DEBIAN-CVE-2026-123829 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 5 more | nodejs | no fix listed | UBUNTU-CVE-2026-123829 |
| Red Hat | hummingbird:1 | nodejs22, nodejs22-bin, nodejs22-docs and 4 more | 1:22.23.5-2.3.2.3.1.hum1 | RHSA-2026:99433 |
| Red Hat | hummingbird:1 | nodejs22-npm | 1:10.9.9-1.22.23.5.2.3.2.3.1.hum1 | RHSA-2026:99433 |
| Red Hat | hummingbird:1 | nodejs24, nodejs24-bin, nodejs24-docs and 3 more | 1:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm | 2:11.19.1-1.24.22.3.0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm-bin | 2:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs26, nodejs26-bin, nodejs26-docs and 4 more | 1:26.13.1-0.1.hum1 | RHSA-2026:99436 |
| Red Hat | hummingbird:1 | nodejs26-npm | 1:11.20.0-1.26.13.1.0.1.hum1 | RHSA-2026:99436 |
| Alpine | v3.21, v3.22 | nodejs | 22.23.5-r0 | ALPINE-CVE-2026-123829 |
| Alpine | v3.23, v3.24 | nodejs | 24.22.3-r0 | ALPINE-CVE-2026-123829 |
| Alpine | v3.24 | nodejs-current | 26.13.1-r0 | ALPINE-CVE-2026-123829 |
| Alpaquita | stream | nodejs22 | 22.23.5-r0 | BELL-CVE-2026-123829 |
| Alpaquita | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-123829 |
| Alpaquita | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-123829 |
| BellSoft Hardened Containers | stream | nodejs22 | 22.23.5-r0 | BELL-CVE-2026-123829 |
| BellSoft Hardened Containers | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-123829 |
| BellSoft Hardened Containers | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-123829 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine · Alpaquita · BellSoft Hardened Containers.
Red Hat
Red Hat rates this Low.
This vulnerability is rated as Low severity because the flaw is confined to local environments, demands specific non-default execution flags, and only leaks filesystem metadata such as names and timestamps rather than actual file data. In typical Red Hat deployments on Linux systems, the native backend monitoring mechanisms implicated in this issue are not utilized, eliminating exposure. Consequently, standard production workloads running Node.js on supported Red Hat platforms remain unaffected.
On Linux this issue does not apply. On macOS/Windows under --permission, avoid recursive fs.watch() on directories with narrower descendant read grants, or intentionally broaden the read grant to cover watched descendants.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | nodejs22 | Not affected | |
| Red Hat Enterprise Linux 10 | nodejs24 | Not affected | |
| Red Hat Enterprise Linux 10 | nodejs26 | Not affected | |
| Red Hat Enterprise Linux 8 | nodejs:22/nodejs | Not affected | |
| Red Hat Enterprise Linux 8 | nodejs:24/nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs:22/nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs:24/nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs:26/nodejs | Not affected | |
| Red Hat Hardened Images | hi/nodejs | Under investigation | |
| Red Hat Hardened Images | nodejs20 | Fix deferred | |
| Red Hat Hardened Images | nodejs22 | Affected | |
| Red Hat Hardened Images | nodejs24 | Affected | |
| Red Hat Hardened Images | nodejs25 | Fix deferred | |
| Red Hat Hardened Images | nodejs26 | Affected | |
| Red Hat Hardened Images | npm12 | Under investigation |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-123829.
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).