How severe is CVE-2024-10389?

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

Which packages are affected by CVE-2024-10389?

CVE-2024-10389 affects the following packages: github.com/google/safearchive (Go). Ecosystems affected: Go.

How do I fix CVE-2024-10389?

Update github.com/google/safearchive to 0.0.0-20241025131057-f7ce9d7b6f9c or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-10389 is resolved across your whole dependency graph.

How do I detect CVE-2024-10389 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/safearchive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-10389 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-2024-10389 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-10389 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-2024-10389?

CVE-2024-10389 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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-2024-10389?

CVE-2024-10389 is classified as CWE-427 (CWE-427), Path Traversal (CWE-22). These weakness types 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-2024-10389 published, and has it been updated?

CVE-2024-10389 was published on November 4, 2024 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-2024-10389 — safearchive

Fix: google/safearchive@f7ce9d7

CVE-2024-10389 is a CWE-427 vulnerability in github.com/google/safearchive. A fix is available for github.com/google/safearchive — see the affected versions and patch details below.

Path Traversal in Safearchive

Also known asGHSA-q3rp-vvm7-j8jgGO-2024-3251

Published

Nov 4, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 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-2024-10389.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% 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/google/safearchive

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

There exists a Path Traversal vulnerability in Safearchive on Platforms with Case-Insensitive Filesystems (e.g., NTFS). This allows Attackers to Write Arbitrary Files via Archive Extraction containing symbolic links. We recommend upgrading past commit f7ce9d7b6f9c6ecd72d0b0f16216b046e55e44dc

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/google/safearchive`	all versions	0.0.0-20241025131057-f7ce9d7b6f9c`go get github.com/google/safearchive@v0.0.0-20241025131057-f7ce9d7b6f9c`

Affected Products

1 product · 1 configurations

Application

safearchivegoogle

< 2024-10-25

range

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/google/safearchive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/google/safearchive to 0.0.0-20241025131057-f7ce9d7b6f9c or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-10389 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

O3 Security · Impact-Aware SCA

Is CVE-2024-10389 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works