CVE-2026-56847: CWE-1119 Excessive Use of Unconditional Branching in nodejs node
A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects Node.js **22.x**, **24.x**, and **26.x**.
AI Analysis
Technical Summary
CVE-2026-56847 is a low-severity vulnerability in Node.js where the permission model enforcement is flawed. The trace_events.createTracing().enable() function can write trace logs outside the scope restricted by the --allow-fs-write flag, potentially allowing unauthorized file system writes. This could lead to confidentiality issues or bypass of intended security boundaries in affected Node.js versions 22.23.1, 24.18.0, and 26.5.0. No official patch or remediation guidance is currently available from the vendor, and no known exploits are reported in the wild.
Potential Impact
The vulnerability allows trace logs to be written outside the intended permission boundaries, which may cause confidentiality impacts or security boundary bypass under affected configurations. However, the impact is limited as indicated by the low CVSS score (3.3) and the requirement for local privileges (AV:L) and low privileges (PR:L). There is no indication of availability or integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should carefully evaluate the use of trace_events.createTracing().enable() especially in environments where the --allow-fs-write flag is not set. Restricting access to local users and monitoring usage of tracing features may reduce risk.
CVE-2026-56847: CWE-1119 Excessive Use of Unconditional Branching in nodejs node
Description
A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects Node.js **22.x**, **24.x**, and **26.x**.
CVSS v3.0
Score 3.3low
Affected software
pkg:github/nodejs/nodeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-56847 is a low-severity vulnerability in Node.js where the permission model enforcement is flawed. The trace_events.createTracing().enable() function can write trace logs outside the scope restricted by the --allow-fs-write flag, potentially allowing unauthorized file system writes. This could lead to confidentiality issues or bypass of intended security boundaries in affected Node.js versions 22.23.1, 24.18.0, and 26.5.0. No official patch or remediation guidance is currently available from the vendor, and no known exploits are reported in the wild.
Potential Impact
The vulnerability allows trace logs to be written outside the intended permission boundaries, which may cause confidentiality impacts or security boundary bypass under affected configurations. However, the impact is limited as indicated by the low CVSS score (3.3) and the requirement for local privileges (AV:L) and low privileges (PR:L). There is no indication of availability or integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should carefully evaluate the use of trace_events.createTracing().enable() especially in environments where the --allow-fs-write flag is not set. Restricting access to local users and monitoring usage of tracing features may reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-06-23T15:00:03.632Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6aee0c9c2644c7f8a7f058
Added to database: 07/30/2026, 06:24:12 UTC
Last enriched: 07/30/2026, 06:39:34 UTC
Last updated: 07/31/2026, 02:51:53 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.