Permission bypass via unchecked diagnostic report path
Published Jun 18, 2026 · Updated Jun 18, 2026
Improper access control in Node.js allows local users to write diagnostic reports outside permitted paths when the Permission Model is enabled. process.report.writeReport() failed to check fs.write permission for an explicit output path or the current working directory used for its default filename. The affected ranges are 22.0.0 through 22.22.3, 24.0.0 through 24.16.0, and 26.0.0 through 26.3.0; exploitation also requires code execution inside the restricted process.
Summary
What happened
Improper access control in Node.js allows local users to write diagnostic reports outside permitted paths when the Permission Model is enabled. process.report.writeReport() failed to check fs.write permission for an explicit output path or the current working directory used for its default filename. The affected ranges are 22.0.0 through 22.22.3, 24.0.0 through 24.16.0, and 26.0.0 through 26.3.0; exploitation also requires code execution inside the restricted process.
The record
- CVE
- CVE-2026-48617
- Published
- Jun 18, 2026
- Updated
- Jun 18, 2026
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- CWE-284
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 18, 2026CVE publishedPublication date reported by the CVE source.
- Jun 18, 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.22.3 <=22.22.3
- Affected versionversion=24.16.0 <=24.16.0
- Affected versionversion=26.3.0 <=26.3.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