Path traversal in ZIPFoundationGHSA-c2cc-3569-6jh2
HIGHGHSA-c2cc-3569-6jh2 is a high-severity (CVSS 7.8) Path Traversal vulnerability in github.com/weichsel/ZIPFoundation. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/weichsel/ZIPFoundation — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-c2cc-3569-6jh2.
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/weichsel/ZIPFoundationReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects SwiftURL packages — download data is not available via public APIs for these ecosystems.
Description
An issue in ZIPFoundation v0.9.16 allows attackers to execute a path traversal via extracting a crafted zip file.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦SwiftURL | github.com/weichsel/ZIPFoundation | all versions | 0.9.18 |
Affected Products
zipfoundationpeakstepResearch 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/weichsel/ZIPFoundation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/weichsel/ZIPFoundation to 0.9.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c2cc-3569-6jh2 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-c2cc-3569-6jh2 in your dependencies?
Find it across SwiftURL, including transitive dependencies.