Permission bypass via unchecked trace log writes
Published Jul 30, 2026 · Updated Jul 30, 2026
Improper permission enforcement in Node.js 22.x, 24.x, and 26.x allows local users to write trace logs outside allowed paths. NodeCategorySet::Enable starts tracing through trace_events.createTracing().enable() without checking FileSystemWrite permission for the resolved trace-event file path. The bypass requires the Permission Model and local code execution, and it can expose trace data or place trace output beyond the configured write allowlist.
Summary
What happened
Improper permission enforcement in Node.js 22.x, 24.x, and 26.x allows local users to write trace logs outside allowed paths. NodeCategorySet::Enable starts tracing through trace_events.createTracing().enable() without checking FileSystemWrite permission for the resolved trace-event file path. The bypass requires the Permission Model and local code execution, and it can expose trace data or place trace output beyond the configured write allowlist.
The record
- CVE
- CVE-2026-56847
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- CWE-1119
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=22.23.1 <=22.23.1
- Affected versionversion=24.18.0 <=24.18.0
- Affected versionversion=26.5.0 <=26.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo