nodejs Node.js up to 22.23.1/24.18.0/26.5.0 Permission Model permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 1.72 |
Summary
A vulnerability was found in nodejs Node.js up to 22.23.1/24.18.0/26.5.0. It has been rated as critical. Affected by this issue is some unknown functionality of the component Permission Model. This manipulation causes permission. The identification of this vulnerability is CVE-2026-58039. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability has been found in nodejs Node.js up to 22.23.1/24.18.0/26.5.0 and classified as critical. Affected by this vulnerability is an unknown function of the component Permission Model. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A flaw in Node.js Permission Model enforcement allows process.report writes (and overwrites) files outside --allow-fs-write paths. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects Node.js **22.x**, **24.x**, and **26.x**.
It is possible to read the advisory at nodejs.org. This vulnerability is known as CVE-2026-58039 since 06/27/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/31/2026). The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/27/2026 CVE reserved07/31/2026 Advisory disclosed
07/31/2026 VulDB entry created
07/31/2026 VulDB entry last update
Sources
Advisory: nodejs.orgStatus: Not defined
CVE: CVE-2026-58039 (🔒)
GCVE (CVE): GCVE-0-2026-58039
GCVE (VulDB): GCVE-100-384979
Entry
Created: 07/31/2026 02:46Changes: 07/31/2026 02:46 (53)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.