Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w87r-vg9q-crqm | zx Uses Incorrectly-Resolved Name or Reference |
Mon, 24 Nov 2025 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google zx |
|
| Vendors & Products |
Google
Google zx |
Fri, 21 Nov 2025 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Thu, 20 Nov 2025 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 20 Nov 2025 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Arbitrary node_modules Directory Deletion in Google zx | |
| Weaknesses | CWE-706 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: Google
Published:
Updated: 2025-11-20T16:49:32.470Z
Reserved: 2025-11-19T19:03:28.234Z
Link: CVE-2025-13437
Updated: 2025-11-20T16:49:26.587Z
Status : Deferred
Published: 2025-11-20T17:15:49.453
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-13437
OpenCVE Enrichment
Updated: 2025-11-24T09:09:35Z
Github GHSA