CVE-2025-64346 — archives
Fix: jaredallard/archives@3bddec7CVE-2025-64346 is a Path Traversal vulnerability in github.com/jaredallard/archives. A fix is available for github.com/jaredallard/archives — see the affected versions and patch details below.
archives: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64346.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/jaredallard/archivesReal-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
Impact
A malicious user could feed a specially crafted archive to this library causing RCE, modification of files or other bad things in the context of whatever user is running this library as, through the program that imports it.
The severity highly depends on the user's permissions and environment it is being ran in (e.g., non root, read only root container would likely have no impact vs running something as root on a production system).
The severity is also dependent on arbitrary archives being passed or not.
Based on the above, severity high was picked to be safe.
Patches
Patched with the help of snyk and gosec in v1.0.1
Workarounds
The only workaround is to manually validate archives before submitting them to this library, however that is not recommended vs upgrading to unaffected versions.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/jaredallard/archives | all versions | 1.0.1go get github.com/jaredallard/archives@v1.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jaredallard/archives, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/jaredallard/archives to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64346 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-64346 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-64346. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-64346 in your dependencies?
O3 Security finds CVE-2025-64346 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.