CVE-2026-58043: CWE-284 Improper Access Control - Generic in nodejs node
A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries. Under `--permission`, an attacker who is granted access to one path can abuse boundary handling to read from or write to paths outside the intended filesystem allowlist. This vulnerability affects Node.js **main**, **22.x**, **24.x**, and **26.x**.
AI Analysis
Technical Summary
This vulnerability arises from a flaw in the enforcement of the Node.js permission model under the --permission flag. Specifically, the issue is that the boundary handling of filesystem paths using a radix-tree prefix structure is flawed, allowing an attacker who has been granted access to a particular filesystem path to bypass restrictions and access other paths outside the intended allowlist. This improper access control (CWE-284) can lead to unauthorized read and write operations on the filesystem. The affected versions explicitly include Node.js 22.23.1, 24.18.0, and 26.5.0, as well as the main development branch. The CVSS 3.0 score is 7.5, indicating high severity, with an attack vector local, high attack complexity, low privileges required, no user interaction, scope changed, and high impact on confidentiality and integrity but no impact on availability. No known exploits in the wild or vendor patches are currently documented.
Potential Impact
Successful exploitation allows an attacker with limited filesystem permissions to escalate their access beyond the intended scope, potentially reading or modifying sensitive files outside the authorized directories. This compromises confidentiality and integrity of the filesystem data accessible to the Node.js process. There is no indication of availability impact. The vulnerability affects local users with some privileges, requiring high attack complexity.
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 restrict permissions granted under the --permission flag and avoid running untrusted code with elevated filesystem access. Monitor official Node.js channels for updates and apply patches promptly once available.
CVE-2026-58043: CWE-284 Improper Access Control - Generic in nodejs node
Description
A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries. Under `--permission`, an attacker who is granted access to one path can abuse boundary handling to read from or write to paths outside the intended filesystem allowlist. This vulnerability affects Node.js **main**, **22.x**, **24.x**, and **26.x**.
CVSS v3.0
Score 7.5high
Affected software
Run 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
This vulnerability arises from a flaw in the enforcement of the Node.js permission model under the --permission flag. Specifically, the issue is that the boundary handling of filesystem paths using a radix-tree prefix structure is flawed, allowing an attacker who has been granted access to a particular filesystem path to bypass restrictions and access other paths outside the intended allowlist. This improper access control (CWE-284) can lead to unauthorized read and write operations on the filesystem. The affected versions explicitly include Node.js 22.23.1, 24.18.0, and 26.5.0, as well as the main development branch. The CVSS 3.0 score is 7.5, indicating high severity, with an attack vector local, high attack complexity, low privileges required, no user interaction, scope changed, and high impact on confidentiality and integrity but no impact on availability. No known exploits in the wild or vendor patches are currently documented.
Potential Impact
Successful exploitation allows an attacker with limited filesystem permissions to escalate their access beyond the intended scope, potentially reading or modifying sensitive files outside the authorized directories. This compromises confidentiality and integrity of the filesystem data accessible to the Node.js process. There is no indication of availability impact. The vulnerability affects local users with some privileges, requiring high attack complexity.
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 restrict permissions granted under the --permission flag and avoid running untrusted code with elevated filesystem access. Monitor official Node.js channels for updates and apply patches promptly once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-06-27T15:00:00.780Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6aee0c9c2644c7f8a7f061
Added to database: 07/30/2026, 06:24:12 UTC
Last enriched: 07/30/2026, 06:37:13 UTC
Last updated: 07/31/2026, 02:51:54 UTC
Views: 18
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.