CVE-2025-68398
Weblate · Weblate
A critical vulnerability has been identified in the Weblate localization tool, assigned CVE-2025-68398 with a CVSS score of 9.1.
Executive summary
A critical vulnerability has been identified in the Weblate localization tool, assigned CVE-2025-68398 with a CVSS score of 9.1. This flaw allows a remote attacker to overwrite Git configuration files, which can be leveraged to execute arbitrary code on the server. Successful exploitation could lead to a full system compromise, resulting in data theft, service disruption, and unauthorized access to the underlying infrastructure.
Vulnerability
The vulnerability exists due to improper validation of user-supplied input that affects the underlying Git repositories managed by Weblate. A remote attacker can craft a malicious request to overwrite the .git/config file for a specific project repository. By modifying this configuration, an attacker can manipulate Git's behavior, for example, by setting the core.sshCommand or core.hooksPath directives to point to a malicious script, leading to Remote Code Execution (RCE) when Weblate next performs a Git operation (e.g., a pull or push).
Business impact
This vulnerability is rated as critical severity with a CVSS score of 9.1. Successful exploitation could result in a complete compromise of the Weblate server, leading to significant business consequences. These include the theft of sensitive data such as source code, API keys, and user credentials; disruption of critical localization and development workflows; and reputational damage from a public security breach. A compromised server could also be used as a pivot point for attackers to move laterally within the organization's network, escalating the incident's impact.
Remediation
Immediate Action: Organizations must immediately upgrade all vulnerable Weblate instances to the patched version 5.15.1 or later. After applying the update, it is crucial to review access logs and Git repository configurations for any signs of compromise that may have occurred prior to patching, such as unexpected configuration changes or outbound connections.
Proactive Monitoring:
Implement enhanced monitoring for Weblate servers. Security teams should look for suspicious activity in application and system logs, such as unexpected processes being spawned by the Weblate service user. Monitor for unauthorized modifications to .git/config files within project directories and scrutinize outbound network traffic from the Weblate server for connections to unknown or malicious IP addresses, which could indicate a reverse shell.
Compensating Controls: If immediate patching is not feasible, implement the following compensating controls to reduce risk:
- Network Segmentation: Isolate the Weblate server from other critical internal systems.
- Egress Filtering: Restrict all outbound network connections from the server to only known and required destinations to block reverse shell callbacks.
- File Integrity Monitoring (FIM): Deploy FIM solutions to actively monitor
.git/configfiles for any unauthorized changes and alert administrators. - Web Application Firewall (WAF): Configure a WAF with rules to inspect and block malicious patterns in traffic destined for the Weblate instance, if a specific attack pattern becomes known.
Exploitation status
Public Exploit Available: False (as of Dec 18, 2025)
Analyst recommendation
Given the critical severity (CVSS 9.1) of this vulnerability, immediate action is required. We strongly recommend all organizations using affected versions of Weblate prioritize the deployment of the security patch (version 5.15.1 or later) to prevent a potential system compromise. While this CVE is not currently on the CISA KEV list, its characteristics make it a prime candidate for future inclusion. Proactive patching and monitoring are the most effective strategies to protect against this threat.