nodejs Node.js up to 22.23.1/24.18.0/26.5.0 Permission Model privileges management

Summaryinfo

A vulnerability classified as critical has been found in nodejs Node.js up to 22.23.1/24.18.0/26.5.0. The affected element is an unknown function of the component Permission Model. Performing a manipulation results in privileges management. This vulnerability is identified as CVE-2026-58043. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in nodejs Node.js up to 22.23.1/24.18.0/26.5.0. It has been classified as critical. This affects some unknown processing of the component Permission Model. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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**.

The advisory is shared at nodejs.org. This vulnerability is uniquely identified as CVE-2026-58043 since 06/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/30/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• JavaScript Library

Vendor

• nodejs

Name

• Node.js

Version

• 22.23.0
• 22.23.1
• 24.0
• 24.1
• 24.2
• 24.3
• 24.4
• 24.5
• 24.6
• 24.7
• 24.8
• 24.9
• 24.10
• 24.11
• 24.12
• 24.13
• 24.14
• 24.15
• 24.16
• 24.17
• 24.18.0
• 26.0
• 26.1
• 26.2
• 26.3
• 26.4
• 26.5.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion