CVE-2025-67818GHSA-7V39-2HX7-7C43GO-2025-4237
An issue was discovered in Weaviate OSS before 1.33.4.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.30.20, 1.31.19, 1.32.16, 1.33.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- github.com/weaviate/weaviateGo
fixed in 1.30.20
- github.com/weaviate/weaviateGo
From 1.31.0-rc.0 · fixed in 1.31.19
- github.com/weaviate/weaviateGo
From 1.32.0-rc.0 · fixed in 1.32.16
- github.com/weaviate/weaviateGo
From 1.33.0-rc.0 · fixed in 1.33.4
- github.com/weaviate/weaviateGo
fixed in 1.30.20; From 1.31.0-rc.0 · fixed in 1.31.19; From 1.32.0-rc.0 · fixed in 1.32.16; From 1.33.0-rc.0 · fixed in 1.33.4