A flaw in Node.js Permission Model enforcement allows Bypass via process.report.writeReport() Path Misvalidation. (CVE-2026-48617)
A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
AI Analysis
Technical Summary
CVE-2026-48617 is a vulnerability in Node.js's experimental Permission Model, which restricts filesystem, network, and process access when enabled via the --permission flag. The flaw arises from insufficient path validation in the process.report.writeReport() function, allowing an attacker to bypass intended security boundaries and write diagnostic reports to unauthorized locations. This can lead to unauthorized information disclosure under specific configurations. The vulnerability is low severity and only affects systems with the Permission Model enabled. Fixed Node.js releases 22.23.0, 24.17.0, and 26.3.1 and later address this issue. Red Hat Hardened Images include updated RPMs to remediate this vulnerability.
Potential Impact
The vulnerability allows bypassing the Permission Model's enforcement, enabling code with restricted permissions to write diagnostic reports outside the configured allow-list. This can result in low-severity information disclosure. The flaw does not affect Node.js when the Permission Model is not enabled. There are no known exploits in the wild. The impact is limited to confidentiality under specific configurations.
Mitigation Recommendations
A fix is available. Users relying on the Permission Model should upgrade to Node.js versions 22.23.0, 24.17.0, or 26.3.1 and later as provided by their downstream vendors, including Red Hat Hardened Images RPM updates. No workaround is available for restricting process.report.writeReport() output paths. Applying the update is the recommended mitigation.
A flaw in Node.js Permission Model enforcement allows Bypass via process.report.writeReport() Path Misvalidation. (CVE-2026-48617)
Description
A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48617 is a vulnerability in Node.js's experimental Permission Model, which restricts filesystem, network, and process access when enabled via the --permission flag. The flaw arises from insufficient path validation in the process.report.writeReport() function, allowing an attacker to bypass intended security boundaries and write diagnostic reports to unauthorized locations. This can lead to unauthorized information disclosure under specific configurations. The vulnerability is low severity and only affects systems with the Permission Model enabled. Fixed Node.js releases 22.23.0, 24.17.0, and 26.3.1 and later address this issue. Red Hat Hardened Images include updated RPMs to remediate this vulnerability.
Potential Impact
The vulnerability allows bypassing the Permission Model's enforcement, enabling code with restricted permissions to write diagnostic reports outside the configured allow-list. This can result in low-severity information disclosure. The flaw does not affect Node.js when the Permission Model is not enabled. There are no known exploits in the wild. The impact is limited to confidentiality under specific configurations.
Mitigation Recommendations
A fix is available. Users relying on the Permission Model should upgrade to Node.js versions 22.23.0, 24.17.0, or 26.3.1 and later as provided by their downstream vendors, including Red Hat Hardened Images RPM updates. No workaround is available for restricting process.report.writeReport() output paths. Applying the update is the recommended mitigation.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2026:46197
- Cve Count
- 1
- State
- PUBLISHED
Threat ID: 6a74cfabbf8831d5391b1a83
Added to database: 08/06/2026, 18:17:15 UTC
Last enriched: 09/07/2026, 17:14:38 UTC
Last updated: 09/21/2026, 22:01:35 UTC
Views: 52
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.
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.