CVE-2025-68398 is a critical (CVSS 9.1) flaw in Weblate, the web based localization tool. Before version 5.15.1, it was possible to overwrite Git configuration remotely and override some of its behavior. The advisory titles the result remote code execution. Upgrade to Weblate 5.15.1 or later.
What's affected
Weblate versions before 5.15.1. The fixed version is 5.15.1, per the record and the GitHub advisory GHSA-8vcg-cfxj-p5m3.
The advisory lists CVSS 3.1 base score 9.1 with the vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Note the privileges required value is high, so the attacker needs an account with significant rights in Weblate, and the scope is changed, which is part of why the score lands in critical. The record and the advisory agree on the score and on the affected and fixed versions.
The advisory does not list a workaround. Upgrading is the only remediation it gives. It also does not say the flaw has been exploited, and the CISA Known Exploited Vulnerabilities flag in the record is false.
How to check if you're exposed
Find your Weblate version. For a pip install:
pip show weblate
For a container deployment, look at the image tag you run and compare it with 5.15.1:
docker ps --format "table {{.Names}}\t{{.Image}}"
If you pin Weblate in a requirements file or lock file, search for the version there too:
grep -rn "weblate" requirements*.txt poetry.lock Pipfile.lock 2>/dev/null
Anything below 5.15.1 is in scope. Weblate often runs as a shared internal service, so also ask whether a second instance exists for a team that set it up on its own.
What to do now
- Upgrade every Weblate instance to 5.15.1 or later, following the project's upgrade notes for your install method.
- Review who holds high privileges in Weblate, since the CVSS vector assumes a privileged account. Remove accounts you do not recognize.
- Check that the user the Weblate process runs as has only the file access it needs, and that secrets such as repository credentials are scoped tightly.
- If you cannot upgrade today, limit network access to the instance to trusted users, and note the advisory lists no workaround.
- Record the change so a later audit can show when the fix went in.
Why it matters
The advisory text is short. It says the issue allowed overwriting Git configuration remotely to change how Git behaves. The record lists CWE-20 (improper input validation), CWE-22 (path traversal) and CWE-434 (unrestricted upload of file with dangerous type). I did not find a detailed root cause on the advisory page, so this post does not describe one.
Git configuration is a sensitive target because Git can be told to run helper programs. That is general knowledge about Git, not something this advisory spells out in detail, but it explains why a configuration overwrite on a server that clones and manages repositories is treated as a path to code execution. A localization tool also holds source repositories and credentials for pushing translations back, so a compromised instance is a good foothold for further access.
Tools that sit beside your code, such as translation platforms, are often left out of patch routines because they are not in the production request path. Putting them in your software inventory is the first step. The fix here is a normal version bump, which makes it cheap to do now.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which Weblate version fixes CVE-2025-68398?
Version 5.15.1. Versions before it are affected.
Does the attacker need an account?
The CVSS vector in the advisory lists privileges required as high, so a privileged account is assumed. Treat that as a reason to review accounts, not as a reason to delay the upgrade.
Sources
- Safeguard Gold entry for CVE-2025-68398
- Weblate GitHub security advisory GHSA-8vcg-cfxj-p5m3
- Weblate 5.15.1 release
- Fix pull request 17330
- Fix pull request 17345
Last reviewed: 18 October 2026.
