Node.js up to 22.23.1/24.18.0/26.5.0 Permission Model trace_events.createTracing.enable permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 1.30 |
Summary
A vulnerability described as critical has been identified in Node.js up to 22.23.1/24.18.0/26.5.0. Impacted is the function trace_events.createTracing.enable of the component Permission Model. Such manipulation leads to permission.
This vulnerability is referenced as CVE-2026-56847. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Node.js up to 22.23.1/24.18.0/26.5.0 and classified as critical. Affected by this issue is the function trace_events.createTracing.enable of the component Permission Model. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality, integrity, and availability. CVE summarizes:
A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. 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**.
The advisory is shared for download at nodejs.org. This vulnerability is handled as CVE-2026-56847 since 06/23/2026. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/30/2026). The MITRE ATT&CK project declares the attack technique as T1222.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
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/23/2026 CVE reserved07/30/2026 Advisory disclosed
07/30/2026 VulDB entry created
07/30/2026 VulDB entry last update
Sources
Advisory: nodejs.orgStatus: Not defined
CVE: CVE-2026-56847 (🔒)
GCVE (CVE): GCVE-0-2026-56847
GCVE (VulDB): GCVE-100-384620
Entry
Created: 07/30/2026 09:23Changes: 07/30/2026 09:23 (53)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.