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

Path Traversal in w-zipGHSA-fr6q-jv7j-35g3

CRITICALFix: yuda-lyu/w-zip@d7039d0

GHSA-fr6q-jv7j-35g3 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in w-zip. 1 public exploit reference exists, so weaponization risk is real. A fix is available for w-zip — see the affected versions and patch details below.

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

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.18%0.83%1.48%2.12%0.7%1.6%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-fr6q-jv7j-35g3 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% 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.

3other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
w-zipnpm
267downloads / week

Description

Path Traversal in NPM w-zip prior to 1.0.12.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmw-zipall versions1.0.12npm install w-zip@1.0.12

Affected Products

1 product · 1 configurations
Application
w-zipw-zip_project
< 1.0.12
range
Exploits & PoCs
1

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

Path Traversal in NPM w-zip prior to 1.0.12.

huntr.devNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update w-zip to 1.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fr6q-jv7j-35g3 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Path Traversal in NPM w-zip prior to 1.0.12.
O3 Security · Impact-Aware SCA

Is GHSA-fr6q-jv7j-35g3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Path Traversal in w-zip (Critical 9.8)