How severe is GHSA-wp3j-gv53-4pg8?

GHSA-wp3j-gv53-4pg8 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-wp3j-gv53-4pg8?

GHSA-wp3j-gv53-4pg8 affects the following packages: fs-git (npm). Ecosystems affected: npm.

How do I fix GHSA-wp3j-gv53-4pg8?

Update fs-git to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wp3j-gv53-4pg8 is resolved across your whole dependency graph.

How do I detect GHSA-wp3j-gv53-4pg8 in my npm dependencies?

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

How do I mitigate GHSA-wp3j-gv53-4pg8 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-wp3j-gv53-4pg8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wp3j-gv53-4pg8 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-wp3j-gv53-4pg8?

GHSA-wp3j-gv53-4pg8 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th 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.

When was GHSA-wp3j-gv53-4pg8 published, and has it been updated?

GHSA-wp3j-gv53-4pg8 was published on May 13, 2022 and was last updated on November 8, 2023. 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

HIGH severity

fs-git command injection vulnerabilityGHSA-wp3j-gv53-4pg8

HIGHFix: vvakame/fs-git@eb5f70e

GHSA-wp3j-gv53-4pg8 is a high-severity (CVSS 7.8) remote code execution vulnerability in fs-git. A fix is available for fs-git — see the affected versions and patch details below.

Also known asCVE-2017-1000451

Published

May 13, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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.

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

fs-gitnpm

152downloads / week

Description

fs-git is a file system like api for git repository. The fs-git version 1.0.1 module relies on child_process.exec, however, the buildCommand method used to construct exec strings does not properly sanitize data and is vulnerable to command injection across all methods that use it and call exec.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`fs-git`	all versions	1.0.2`npm install fs-git@1.0.2`

Affected Products

1 product · 1 configurations

Application

fs-gitfs-git_project

≤ 1.0.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fs-git, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fs-git to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wp3j-gv53-4pg8 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-wp3j-gv53-4pg8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works