Arbitrary File Write via Archive Extraction in mholt/archiverGHSA-5wmg-j84w-4jj4
MEDIUMFix: mholt/archiver#65GHSA-5wmg-j84w-4jj4 is a medium-severity (CVSS 5.5) Path Traversal vulnerability in github.com/mholt/archiver. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/mholt/archiver — see the affected versions and patch details below.
EPSS Exploitation Probability
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
github.com/mholt/archiverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
mholt/archiver golang package before e4ef56d48eb029648b0e895bb0b6a393ef0829c3 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in an archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mholt/archiver | all versions | 2.1.0go get github.com/mholt/archiver@v2.1.0 |
Affected Products
archiverarchiver_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mholt/archiver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mholt/archiver to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wmg-j84w-4jj4 is resolved across your whole dependency graph.
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
Is GHSA-5wmg-j84w-4jj4 in your dependencies?
Find it across Go, including transitive dependencies.