GHSA-7v39-2hx7-7c43 — weaviate
Fix: weaviate/weaviate@169df2dGHSA-7v39-2hx7-7c43 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.
Weaviate OSS has a Path Traversal Vulnerability via Backup ZipSlip
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-7v39-2hx7-7c43.
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/weaviate/weaviate🐹github.com/weaviate/weaviate🐹github.com/weaviate/weaviate🐹github.com/weaviate/weaviateReal-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. An attacker with access to insert data into the database can craft an entry name with an absolute path (e.g., /etc/...) or use parent directory traversal (../../..) to escape the restore root when a backup is restored, potentially creating or overwriting files in arbitrary locations within the application's privilege scope.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/weaviate/weaviate | all versions | 1.30.20go get github.com/weaviate/weaviate@v1.30.20 |
| 🐹Go | github.com/weaviate/weaviate | ≥ 1.31.0-rc.0&&< 1.31.19 | 1.31.19go get github.com/weaviate/weaviate@v1.31.19 |
| 🐹Go | github.com/weaviate/weaviate | ≥ 1.32.0-rc.0&&< 1.32.16 | 1.32.16go get github.com/weaviate/weaviate@v1.32.16 |
| 🐹Go | github.com/weaviate/weaviate | ≥ 1.33.0-rc.0&&< 1.33.4 | 1.33.4go get github.com/weaviate/weaviate@v1.33.4 |
Detection & mitigation playbook
Open-source dependencyDetect
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-7v39-2hx7-7c43 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 GHSA-7v39-2hx7-7c43 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7v39-2hx7-7c43. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7v39-2hx7-7c43 in your dependencies?
O3 Security finds GHSA-7v39-2hx7-7c43 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.