Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-8298 — fs-path

CRITICALFix: pillys/fs-path#6

CVE-2020-8298 is a critical-severity (CVSS 9.8) CWE-77 vulnerability in fs-path. 2 public exploit references exist, so weaponization risk is real. A fix is available for fs-path — see the affected versions and patch details below.

Command injection in fs-path

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
11.2%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk
2.07%5.80%9.54%13.3%4.2%11.2%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-8298 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

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
4Kdownloads / week

Description

fs-path node module before 0.0.25 is vulnerable to command injection by way of user-supplied inputs via the copy, copySync, remove, and removeSync methods.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmfs-pathall versions0.0.25npm install fs-path@0.0.25

Affected Products

1 product · 1 configurations
Application
fs-pathfs-path_project
< 0.0.25
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

fs-path node module before 0.0.25 is vulnerable to command injection by …

github.comNVDMar 2021

fs-path node module before 0.0.25 is vulnerable to command injection by …

hackerone.comNVDMar 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

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

  3. 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

fs-path node module before 0.0.25 is vulnerable to command injection by way of user-supplied inputs via the `copy`, `copySync`, `remove`, and `removeSync` methods.
O3 Security · Impact-Aware SCA

Is CVE-2020-8298 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-8298: fs-path — Fixed in 0.0.25