Quick answers
- Is CVE-2026-77573 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77573 being exploited in the wild.
- How severe is CVE-2026-77573?
- Low severity, with a CVSS score of 3.5, published 26 August 2026.
- Which products and versions are affected?
- Weblate Weblate prior to 2026.8.
- Is there a fix for CVE-2026-77573?
- A patch was published on 2026-08-26: Fixed in version 2026.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77573 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-77573?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a server-side request forgery (SSRF) caused by a time-of-check-time-of-use (TOCTOU) race condition in VCS repository URL validation. Weblate validates repository hostnames by performing a DNS resolution in Python, but external VCS clients (Git, Mercurial, Subversion) perform a separate DNS lookup when actually connecting. An attacker-controlled hostname can initially resolve to a public IP to pass validation, then be re-pointed to an internal/private address before the VCS client connects. The attacker must have permission to create or edit component repository URLs and be able to trigger clone, fetch, push, or similar remote VCS operations. Exploitation is mitigated when VCS_RESTRICT_PRIVATE is enabled and untrusted hostnames are not permitted. The issue is fixed in version 2026.8 by pinning addresses at validation time into subsequent protected operations.
Affected products
- Weblate Weblate prior to 2026.8
Timeline
- 2026-08-26: disclosed
- 2026-08-26: patched: Fixed in version 2026.8