Authenticated code execution via restored VCS hooks
Published Apr 15, 2026 · Updated Apr 15, 2026
Code injection in Weblate before 5.17 allows remote authenticated users with project-creation rights to execute code through a crafted backup. The project-backup restore path extracted attacker-supplied Git and Mercurial configuration, including executable Git hooks, instead of rebuilding trusted VCS settings. Exploitation requires permission to create a project and restore its backup, after which a restored hook executes with the Weblate service's privileges.
Summary
What happened
Code injection in Weblate before 5.17 allows remote authenticated users with project-creation rights to execute code through a crafted backup. The project-backup restore path extracted attacker-supplied Git and Mercurial configuration, including executable Git hooks, instead of rebuilding trusted VCS settings. Exploitation requires permission to create a project and restore its backup, after which a restored hook executes with the Weblate service's privileges.
The record
- CVE
- CVE-2026-33435
- Published
- Apr 15, 2026
- Updated
- Apr 15, 2026
- Vendor
- Weblate
- Product
- Weblate
- Classifications
- CWE-23, CWE-94, CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 15, 2026CVE publishedPublication date reported by the CVE source.
- Apr 15, 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
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