SSRF via VCS hostname re-resolution
Published Aug 26, 2026 · Updated Aug 27, 2026
SSRF in Weblate before 2026.8 allows remote authenticated users to reach internal VCS services through repository DNS rebinding. Weblate validates the hostname's initial DNS answer, but external VCS clients resolve it again and connect after an attacker changes it to a private address. Exploitation requires repository-URL management permission, a triggered VCS operation, untrusted hostnames, and VCS_RESTRICT_PRIVATE=True; private repository contents can be exposed.
Summary
What happened
SSRF in Weblate before 2026.8 allows remote authenticated users to reach internal VCS services through repository DNS rebinding. Weblate validates the hostname's initial DNS answer, but external VCS clients resolve it again and connect after an attacker changes it to a private address. Exploitation requires repository-URL management permission, a triggered VCS operation, untrusted hostnames, and VCS_RESTRICT_PRIVATE=True; private repository contents can be exposed.
The record
- CVE
- CVE-2026-77573
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- Vendor
- Weblate
- Product
- Weblate
- Classifications
- CWE-918, CWE-367, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2026.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo