File overwrite via unchecked process.report output path
Published Jul 31, 2026 · Updated Jul 31, 2026
Improper access control in Node.js 22.x, 24.x, and 26.x allows local users to overwrite files outside configured write paths. process.report accepts an attacker-selected output path and writes the diagnostic report without applying the Permission Model's final filesystem-write check. Exploitation requires the Permission Model and attacker-controlled JavaScript in the process; operating-system permissions still bound writable destinations.
Summary
What happened
Improper access control in Node.js 22.x, 24.x, and 26.x allows local users to overwrite files outside configured write paths. process.report accepts an attacker-selected output path and writes the diagnostic report without applying the Permission Model's final filesystem-write check. Exploitation requires the Permission Model and attacker-controlled JavaScript in the process; operating-system permissions still bound writable destinations.
The record
- CVE
- CVE-2026-58039
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- CWE-284, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 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?
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