Authenticated SSRF via unvalidated backup repository URLs
Published May 7, 2026 · Updated May 7, 2026
SSRF in Weblate before 5.17.1 allows remote authenticated users with project.add permission to access private network resources. Backup import bulk-creates Component records without full_clean, skipping validate_repo_url before writing the supplied repository URL into .git/config. Project-creation permission is required; crafted private-address or disallowed-scheme URLs can make the server access resources outside the user's direct reach.
Summary
What happened
SSRF in Weblate before 5.17.1 allows remote authenticated users with project.add permission to access private network resources. Backup import bulk-creates Component records without full_clean, skipping validate_repo_url before writing the supplied repository URL into .git/config. Project-creation permission is required; crafted private-address or disallowed-scheme URLs can make the server access resources outside the user's direct reach.
The record
- CVE
- CVE-2026-41654
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- Weblate
- Product
- Weblate
- Classifications
- CWE-20, CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 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=< 5.17.1
What conditions does exploitation require?
What is affected?
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