How severe is CVE-2025-64346?

No CVSS score has been assigned to CVE-2025-64346 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-64346?

CVE-2025-64346 affects the following packages: github.com/jaredallard/archives (Go). Ecosystems affected: Go.

How do I fix CVE-2025-64346?

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.

How do I detect CVE-2025-64346 in my Go dependencies?

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.

How do I mitigate CVE-2025-64346 if there is no patch (or I can't update yet)?

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.

Is CVE-2025-64346 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-64346 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.

What is the EPSS score for CVE-2025-64346?

CVE-2025-64346 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-64346?

CVE-2025-64346 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-64346 published, and has it been updated?

CVE-2025-64346 was published on November 7, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-64346 — archives

Fix: jaredallard/archives@3bddec7

CVE-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')

Also known asGHSA-j95m-rcjp-q69hGO-2025-3581

Published

Nov 7, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/jaredallard/archives

Real-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

https://security.snyk.io/research/zip-slip-vulnerability

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/jaredallard/archives`	all versions	1.0.1`go get github.com/jaredallard/archives@v1.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
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
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

### 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

O3 Security · Impact-Aware SCA

Is CVE-2025-64346 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works