How severe is GHSA-w87r-vg9q-crqm?

No CVSS score has been assigned to GHSA-w87r-vg9q-crqm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w87r-vg9q-crqm?

GHSA-w87r-vg9q-crqm affects the following packages: zx (npm). Ecosystems affected: npm.

How do I fix GHSA-w87r-vg9q-crqm?

Update zx to 8.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w87r-vg9q-crqm is resolved across your whole dependency graph.

How do I detect GHSA-w87r-vg9q-crqm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w87r-vg9q-crqm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-w87r-vg9q-crqm actively exploited in the wild?

No public exploit code has been indexed for GHSA-w87r-vg9q-crqm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w87r-vg9q-crqm?

GHSA-w87r-vg9q-crqm has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 0th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w87r-vg9q-crqm?

GHSA-w87r-vg9q-crqm is classified as CWE-706 (CWE-706). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w87r-vg9q-crqm published, and has it been updated?

GHSA-w87r-vg9q-crqm was published on November 20, 2025 and was last updated on November 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

zx Uses Incorrectly-Resolved Name or Reference

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w87r-vg9q-crqm.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs0th percentile — riskier than 0% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

858other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

zxnpm

2.8Mdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`zx`	all versions	8.8.5`npm install zx@8.8.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zx to 8.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w87r-vg9q-crqm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-w87r-vg9q-crqm (CC BY 4.0)

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-w87r-vg9q-crqm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

zx Uses Incorrectly-Resolved Name or ReferenceGHSA-w87r-vg9q-crqm