How severe is GHSA-hmmh-292h-3364?

No CVSS score has been assigned to GHSA-hmmh-292h-3364 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hmmh-292h-3364?

GHSA-hmmh-292h-3364 affects the following packages: github.com/weaviate/weaviate (Go), github.com/weaviate/weaviate (Go), github.com/weaviate/weaviate (Go), github.com/weaviate/weaviate (Go). Ecosystems affected: Go.

How do I fix GHSA-hmmh-292h-3364?

Update github.com/weaviate/weaviate to 1.30.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hmmh-292h-3364 is resolved across your whole dependency graph.

How do I detect GHSA-hmmh-292h-3364 in my Go dependencies?

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

How do I mitigate GHSA-hmmh-292h-3364 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 GHSA-hmmh-292h-3364 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hmmh-292h-3364 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 GHSA-hmmh-292h-3364?

GHSA-hmmh-292h-3364 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th 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 GHSA-hmmh-292h-3364?

GHSA-hmmh-292h-3364 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 GHSA-hmmh-292h-3364 published, and has it been updated?

GHSA-hmmh-292h-3364 was published on December 12, 2025 and was last updated on December 18, 2025. 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

Weaviate OSS has path traversal vulnerability via the Shard Movement APIGHSA-hmmh-292h-3364

Fix: weaviate/weaviate@4ff2cc8

GHSA-hmmh-292h-3364 is a Path Traversal vulnerability in github.com/weaviate/weaviate. A fix is available for github.com/weaviate/weaviate — see the affected versions and patch details below.

Also known asCVE-2025-67819GO-2025-4238

Published

Dec 12, 2025

Updated

Dec 18, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 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 GHSA-hmmh-292h-3364.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

🐹github.com/weaviate/weaviate🐹github.com/weaviate/weaviate🐹github.com/weaviate/weaviate🐹github.com/weaviate/weaviate

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

An issue was discovered in Weaviate OSS before 1.33.4. Due to a lack of validation of the fileName field in the transfer logic, an attacker who can call the GetFile method while a shard is in the "Pause file activity" state and the FileReplicationService is reachable can read arbitrary files accessible to the service process.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/weaviate/weaviate`	≥ 1.30.0&&< 1.30.20	1.30.20`go get github.com/weaviate/weaviate@v1.30.20`
🐹Go	`github.com/weaviate/weaviate`	≥ 1.31.0-rc.0&&< 1.31.19	1.31.19`go get github.com/weaviate/weaviate@v1.31.19`
🐹Go	`github.com/weaviate/weaviate`	≥ 1.32.0-rc.0&&< 1.32.16	1.32.16`go get github.com/weaviate/weaviate@v1.32.16`
🐹Go	`github.com/weaviate/weaviate`	≥ 1.33.0-rc.0&&< 1.33.4	1.33.4`go get github.com/weaviate/weaviate@v1.33.4`

Affected Products

1 product · 4 configurations

Application

weaviateweaviate

≥ 1.33.0 && ≤ 1.33.3

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/weaviate/weaviate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/weaviate/weaviate to 1.30.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hmmh-292h-3364 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 GHSA-hmmh-292h-3364 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works