Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.13% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-123829High confidence
Node.js is vulnerable to Permission Model file-name disclosure via recursive fs.watch
nodejs · node
2.5LowCVSS 3.0
Patch only the product branches with a verified fix
Fix availability varies by productLow technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Low, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs nodejs node and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 2 affected or under-investigation product states without a fixed product state in the same current advisory
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-123829 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynodejs: Node.js: Information disclosure via improper permission checks in recursive file watching
The vendor explicitly identifies these products as affected by this CVE.
- nodejs20.src as a component of Red Hat Hardened Images
- nodejs25.src as a component of Red Hat Hardened Images
- Summary
- A flaw was found in Node.js. When recursive file watching is used on macOS and Windows systems, the Node.js Permission Model checks read permissions only on the root directory being monitored rather than validating each nested path. A local process running with restricted permissions can exploit this behavior to observe file system events in unauthorized subdirectories. This flaw leads to information disclosure by exposing restricted file and directory names as well as event timing metadata, although it does not expose actual file contents.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Exposure of Sensitive Information to an Unauthorized Actor → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-200 ↗
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:NCommon Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- Fixed
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@src as a component of Red Hat Hardened Images
- nodejs22-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images
- nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- nodejs24-1:24.22.3-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- nodejs24-1:24.22.3-0.1.hum1@s390x as a component of Red Hat Hardened Images
- nodejs24-1:24.22.3-0.1.hum1@src as a component of Red Hat Hardened Images
- nodejs24-1:24.22.3-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- nodejs24-bin-1:24.22.3-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- and 45 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 11 Nov 2026 · Last source change 11 Nov 2026, 18:12 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-11-12
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceNo official EUVD mapping
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-123829 to remediation: access.redhat.com/CVE-2026-123829.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-123829
- After
- remediation: access.redhat.com/CVE-2026-123829
- Remediation statusRemediation status changed from Mitigation available to Patch available.Red Hat Product Security ↗
- Before
- Mitigation available
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- nodejs20.src as a component of Red Hat Hardened Images; nodejs22.src as a component of Red Hat Hardened Images; nodejs24.src as a component of Red Hat Hardened Images; nodejs25.src as a component of Red Hat Hardened Images; nodejs26.src as a component of Red Hat Hardened Images
- After
- nodejs20.src as a component of Red Hat Hardened Images; nodejs25.src as a component of Red Hat Hardened Images · Fixed: nodejs22-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-1:22.23.5-2.3.2.3.1.hum1@src as a component of Red Hat Hardened Images; nodejs22-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@src as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs24-bin-1:24.22.3-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; and 45 more
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-123829 to remediation: access.redhat.com/CVE-2026-123829.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-123829
- After
- remediation: access.redhat.com/CVE-2026-123829
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.