unzip-stream allows Arbitrary File Write via artifact extractionGHSA-6jrj-vc65-c983
HIGHFix: mhr3/unzip-stream@ab67989GHSA-6jrj-vc65-c983 is a high-severity (CVSS 7.5) vulnerability in unzip-stream. A fix is available for unzip-stream — see the affected versions and patch details below.
Real-World Exposure
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.
unzip-streamnpmDescription
Impact
When using the Extract() method of unzip-stream, malicious zip files were able to write to paths they shouldn't be allowed to.
Patches
Fixed in 0.3.2
References
- https://snyk.io/research/zip-slip-vulnerability
- https://github.com/mhr3/unzip-stream/compare/v0.3.1...v0.3.2
Credits
Justin Taft from Google
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | unzip-stream | all versions | 0.3.2npm install unzip-stream@0.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for unzip-stream, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update unzip-stream to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6jrj-vc65-c983 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.
Frequently Asked Questions
Is GHSA-6jrj-vc65-c983 in your dependencies?
Find it across npm, including transitive dependencies.