CVE-2025-66407: Weblate has a Server-Side Request Forgery issue
Impact The Create Component functionality in Weblate allows authorized users to add new translation components by specifying both a version control system and a source code repository URL to pull from. However, the repository URL field is not validated or sanitized, allowing an attacker to supply arbitrary protocols, hostnames, and IP addresses, including localhost, internal network addresses, and local filenames.
Published May 26, 2026
Affected packages
Weblate
- Ecosystem
- PyPI
- Affected
- < 5.15
- Fixed in
- 5.15
- Check
pip show Weblate
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The Create Component functionality in Weblate allows authorized users to add new translation components by specifying both a version control system and a source code repository URL to pull from. However, the repository URL field is not validated or sanitized, allowing an attacker to supply arbitrary protocols, hostnames, and IP addresses, including localhost, internal network addresses, and local filenames.
When the Mercurial version control system is selected, Weblate exposes the full server-side HTTP response for the provided URL. This effectively creates a server-side request forgery (SSRF) primitive that can probe internal services and return their contents. In addition to accessing internal HTTP endpoints, the behavior also enables local file enumeration by attempting file:// requests. While file contents may not always be returned, the application’s error messages clearly differentiate between files that exist and files that do not, revealing information about the server’s filesystem layout.
In cloud environments, this behavior is particularly dangerous, as internal-only endpoints such as cloud metadata services may be accessible, potentially leading to credential disclosure and full environment compromise.
Patches
This has been addressed in the Weblate 5.15 release.
- https://github.com/WeblateOrg/weblate/pull/17103
- https://github.com/WeblateOrg/weblate/pull/17102
Workarounds
Removing Mercurial from VCS_BACKENDS avoids this vulnerability, as the Git backend is not affected. The Git backend was already configured to block the file protocol and does not expose the HTTP response content in the error message.
References
Thanks to Jason Marcello for responsible disclosure.
Credited to secjson, nijel.
References
- https://github.com/WeblateOrg/weblate/security/advisories/GHSA-hfpv-mc5v-p9mm
- https://nvd.nist.gov/vuln/detail/CVE-2025-66407
- https://github.com/WeblateOrg/weblate/pull/17102
- https://github.com/WeblateOrg/weblate/pull/17103
- https://github.com/pypa/advisory-database/tree/main/vulns/weblate/PYSEC-2025-231.yaml
- https://github.com/advisories/GHSA-hfpv-mc5v-p9mm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-55228
Weblate has IDOR in GroupViewSet that allows authenticated project manager to gain unauthorized read access to any private project
high8.1Aug 28, 2026CVE-2026-24126
Weblate has an argument injection in management console
medium6.6Feb 17, 2026CVE-2025-68279
Weblate has an arbitrary file read via symbolic links
high7.7Dec 18, 2025CVE-2025-68398
Weblate is vulnerable to RCE through Git config file overwrite
critical9.1Dec 18, 2025CVE-2025-64725
Weblate has improper validation upon invitation acceptance
low1.0Dec 15, 2025CVE-2025-67492
Weblate's over‑permissive webhook endpoint enables mass repository updates and component enumeration
medium5.3Dec 15, 2025
