CVE-2025-67818: n/a
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.
AI Analysis
Technical Summary
CVE-2025-67818 is a directory traversal vulnerability identified in Weaviate OSS prior to version 1.33.4. The flaw arises during the backup restoration process, where the application fails to properly sanitize or validate entry names inserted into the database. An attacker who can insert data entries can craft names containing absolute paths (e.g., /etc/passwd) or parent directory traversal sequences (../../..) to break out of the designated restore root directory. When the backup is restored, these malicious entries cause files to be created or overwritten outside the intended directory scope, limited only by the application's operating system privileges. This vulnerability is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). The CVSS v3.1 base score is 7.2, indicating high severity, with attack vector as network, low attack complexity, requiring high privileges (database insert rights), no user interaction, and impacting confidentiality, integrity, and availability. Although no exploits have been reported in the wild, the potential for critical system compromise exists if exploited. The vulnerability highlights the importance of input validation and strict privilege separation in backup and restore functionalities.
Potential Impact
For European organizations, this vulnerability poses a significant risk especially to those using Weaviate OSS in production environments for critical data management or AI-driven applications. Exploitation could lead to unauthorized modification or destruction of system files, potentially causing service outages, data breaches, or persistent backdoors. Confidentiality is at risk if sensitive files are overwritten or malicious files planted to exfiltrate data. Integrity is compromised by unauthorized file modifications, and availability could be disrupted by overwriting essential system or application files. Organizations in sectors such as finance, healthcare, and government, which rely on Weaviate OSS for data indexing or AI services, could face operational disruptions and regulatory consequences under GDPR if data integrity or confidentiality is breached. The requirement for authenticated access reduces exposure but insider threats or compromised credentials could enable exploitation.
Mitigation Recommendations
Organizations should immediately upgrade Weaviate OSS to version 1.33.4 or later where this vulnerability is patched. Until patching is possible, restrict database insert permissions to trusted users only and monitor for unusual backup restore activities. Implement strict input validation and sanitization on data entries, especially those used in backup and restore processes. Employ application-level access controls to limit who can perform backup restorations. Use file system permissions to restrict the application's ability to write outside designated directories. Conduct regular audits of backup and restore operations and verify integrity post-restore. Additionally, implement network segmentation and monitoring to detect anomalous behavior indicative of exploitation attempts. Finally, maintain an incident response plan tailored to potential file system compromise scenarios.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Norway, Denmark
CVE-2025-67818: n/a
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-67818 is a directory traversal vulnerability identified in Weaviate OSS prior to version 1.33.4. The flaw arises during the backup restoration process, where the application fails to properly sanitize or validate entry names inserted into the database. An attacker who can insert data entries can craft names containing absolute paths (e.g., /etc/passwd) or parent directory traversal sequences (../../..) to break out of the designated restore root directory. When the backup is restored, these malicious entries cause files to be created or overwritten outside the intended directory scope, limited only by the application's operating system privileges. This vulnerability is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). The CVSS v3.1 base score is 7.2, indicating high severity, with attack vector as network, low attack complexity, requiring high privileges (database insert rights), no user interaction, and impacting confidentiality, integrity, and availability. Although no exploits have been reported in the wild, the potential for critical system compromise exists if exploited. The vulnerability highlights the importance of input validation and strict privilege separation in backup and restore functionalities.
Potential Impact
For European organizations, this vulnerability poses a significant risk especially to those using Weaviate OSS in production environments for critical data management or AI-driven applications. Exploitation could lead to unauthorized modification or destruction of system files, potentially causing service outages, data breaches, or persistent backdoors. Confidentiality is at risk if sensitive files are overwritten or malicious files planted to exfiltrate data. Integrity is compromised by unauthorized file modifications, and availability could be disrupted by overwriting essential system or application files. Organizations in sectors such as finance, healthcare, and government, which rely on Weaviate OSS for data indexing or AI services, could face operational disruptions and regulatory consequences under GDPR if data integrity or confidentiality is breached. The requirement for authenticated access reduces exposure but insider threats or compromised credentials could enable exploitation.
Mitigation Recommendations
Organizations should immediately upgrade Weaviate OSS to version 1.33.4 or later where this vulnerability is patched. Until patching is possible, restrict database insert permissions to trusted users only and monitor for unusual backup restore activities. Implement strict input validation and sanitization on data entries, especially those used in backup and restore processes. Employ application-level access controls to limit who can perform backup restorations. Use file system permissions to restrict the application's ability to write outside designated directories. Conduct regular audits of backup and restore operations and verify integrity post-restore. Additionally, implement network segmentation and monitoring to detect anomalous behavior indicative of exploitation attempts. Finally, maintain an incident response plan tailored to potential file system compromise scenarios.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2025-12-12T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 693c45b972d8eb03a613ec4a
Added to database: 12/12/2025, 4:41:29 PM
Last enriched: 12/19/2025, 5:44:28 PM
Last updated: 2/7/2026, 1:09:23 PM
Views: 114
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2085: Command Injection in D-Link DWR-M921
HighCVE-2026-2084: OS Command Injection in D-Link DIR-823X
HighCVE-2026-2083: SQL Injection in code-projects Social Networking Site
MediumCVE-2026-2082: OS Command Injection in D-Link DIR-823X
MediumCVE-2026-2080: Command Injection in UTT HiPER 810
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.