How severe is GHSA-gc94-6w89-hpqr?

No CVSS score has been assigned to GHSA-gc94-6w89-hpqr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gc94-6w89-hpqr?

GHSA-gc94-6w89-hpqr affects the following packages: fs-path (npm). Ecosystems affected: npm.

How do I fix GHSA-gc94-6w89-hpqr?

Update fs-path to 0.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gc94-6w89-hpqr is resolved across your whole dependency graph.

How do I detect GHSA-gc94-6w89-hpqr in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fs-path. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gc94-6w89-hpqr 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.

How does O3 Security protect against GHSA-gc94-6w89-hpqr?

O3 pinpoints whether GHSA-gc94-6w89-hpqr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gc94-6w89-hpqr actively exploited in the wild?

No public exploit code has been indexed for GHSA-gc94-6w89-hpqr 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.

When was GHSA-gc94-6w89-hpqr published, and has it been updated?

GHSA-gc94-6w89-hpqr was published on June 12, 2019 and was last updated on September 16, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-gc94-6w89-hpqr

Fix: pillys/fs-path#5

GHSA-gc94-6w89-hpqr is a remote code execution vulnerability in fs-path. O3 Security confirms whether GHSA-gc94-6w89-hpqr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Command Injection in fs-path

Published

Jun 12, 2019

Updated

Sep 16, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 16, 2021 · OSV.dev, 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.

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

fs-pathnpm

5Kdownloads / week

Description

All versions of fs-path are vulnerable to command injection is unsanitized user input is passed in.

Recommendation

No fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`fs-path`	all versions	0.0.25

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fs-path. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update fs-path to 0.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gc94-6w89-hpqr 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.
How O3 protects you
O3 pinpoints whether GHSA-gc94-6w89-hpqr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gc94-6w89-hpqr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All versions of `fs-path` are vulnerable to command injection is unsanitized user input is passed in. ## Recommendation No fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.

O3 Security · Impact-Aware SCA

Is GHSA-gc94-6w89-hpqr in your dependencies?

O3 detects GHSA-gc94-6w89-hpqr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works