Google zx 8.8.4 Working Directory src/cli.ts linkNodeModules name resolution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google zx 8.8.4. It has been rated as problematic. Affected by this issue is the function linkNodeModules of the file src/cli.ts of the component Working Directory Handler. Performing a manipulation results in name resolution.
This vulnerability is identified as CVE-2025-13437. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability classified as problematic has been found in Google zx 8.8.4. This affects the function linkNodeModules of the file src/cli.ts of the component Working Directory Handler. The manipulation with an unknown input leads to a name resolution vulnerability. CWE is classifying the issue as CWE-706. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. This is going to have an impact on integrity, and availability. The summary by CVE is:
When zx is invoked with --prefer-local=<path>, the CLI creates a symlink named ./node_modules pointing to <path>/node_modules. Due to a logic error in src/cli.ts (linkNodeModules / cleanup), the function returns the target path instead of the alias (symlink path). The later cleanup routine removes what it received, which deletes the target directory itself. Result: zx can delete an external <path>/node_modules outside the current working directory.
The weakness was released by Ali Firas. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-13437 since 11/19/2025. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/21/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-198297). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
- Product: https://github.com/google/zx/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.4
VulDB Temp Score: 4.4
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: Name resolutionCWE: CWE-706
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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
11/19/2025 CVE reserved11/20/2025 Advisory disclosed
11/20/2025 VulDB entry created
11/21/2025 VulDB entry last update
Sources
Vendor: google.comProduct: github.com
Advisory: github.com
Researcher: Ali Firas
Status: Confirmed
CVE: CVE-2025-13437 (🔒)
GCVE (CVE): GCVE-0-2025-13437
GCVE (VulDB): GCVE-100-333081
EUVD: 🔒
Entry
Created: 11/20/2025 18:05Updated: 11/21/2025 09:19
Changes: 11/20/2025 18:05 (68), 11/20/2025 22:20 (1), 11/21/2025 09:19 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.