How severe is GHSA-73v8-v6g4-vrpm?

No CVSS score has been assigned to GHSA-73v8-v6g4-vrpm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-73v8-v6g4-vrpm?

GHSA-73v8-v6g4-vrpm affects the following packages: decompress-zip (npm), decompress-zip (npm). Ecosystems affected: npm.

How do I fix GHSA-73v8-v6g4-vrpm?

Update decompress-zip to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73v8-v6g4-vrpm is resolved across your whole dependency graph.

How do I detect GHSA-73v8-v6g4-vrpm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decompress-zip. 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-73v8-v6g4-vrpm 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-73v8-v6g4-vrpm?

O3 pinpoints whether GHSA-73v8-v6g4-vrpm 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-73v8-v6g4-vrpm actively exploited in the wild?

No public exploit code has been indexed for GHSA-73v8-v6g4-vrpm 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-73v8-v6g4-vrpm published, and has it been updated?

GHSA-73v8-v6g4-vrpm was published on September 2, 2020 and was last updated on August 31, 2020. 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-73v8-v6g4-vrpm

GHSA-73v8-v6g4-vrpm is a security vulnerability in decompress-zip. O3 Security confirms whether GHSA-73v8-v6g4-vrpm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arbitrary File Overwrite in decompress-zip

Published

Sep 2, 2020

Updated

Aug 31, 2020

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs 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.

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

decompress-zipnpm

113Kdownloads / week

Description

Vulnerable versions of decompress-zip are affected by the Zip-Slip vulnerability, an arbitrary file write vulnerability. The vulnerability occurs because decompress-zip does not verify that extracted files do not resolve to targets outside of the extraction root directory.

Recommendation

For decompress-zip 0.2.x upgrade to 0.2.2 or later. For decompress-zip 0.3.x upgrade to 0.3.2 or later.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`decompress-zip`	all versions	0.2.2
📦npm	`decompress-zip`	≥ 0.3.0&&< 0.3.2	0.3.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decompress-zip. 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 decompress-zip to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73v8-v6g4-vrpm 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-73v8-v6g4-vrpm 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-73v8-v6g4-vrpm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Vulnerable versions of `decompress-zip` are affected by the Zip-Slip vulnerability, an arbitrary file write vulnerability. The vulnerability occurs because `decompress-zip` does not verify that extracted files do not resolve to targets outside of the extraction root directory. ## Recommendation For `decompress-zip` 0.2.x upgrade to 0.2.2 or later. For `decompress-zip` 0.3.x upgrade to 0.3.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-73v8-v6g4-vrpm in your dependencies?

O3 detects GHSA-73v8-v6g4-vrpm 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