Quick answers
- Is CVE-2026-33435 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33435 being exploited in the wild.
- How severe is CVE-2026-33435?
- High severity, with a CVSS score of 8, published 15 April 2026.
- Which products and versions are affected?
- weblate (PyPI) < 5.17, ECOSYSTEM:introduced=0,fixed=5.17.
- Is there a fix for CVE-2026-33435?
- Yes. weblate (PyPI): upgrade to 5.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33435 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-33435?
- Check whether you run weblate (PyPI) or Weblate at an affected version. 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.
How to fix
- weblate (PyPI): upgrade to 5.17 or later
pip install "weblate>=5.17"
Technical details
Weblate versions prior to 5.17 are vulnerable to Remote Code Execution (RCE) via the project backup restoration feature. The vulnerability stems from a failure to filter or neutralize dangerous Git and Mercurial configuration files within the backup archive (CWE-94, CWE-434). An attacker with high privileges (PR:H), such as the ability to create or manage projects, can upload a crafted backup file. During the restoration process, these configuration files can be leveraged to execute arbitrary code on the host system. The attack complexity is considered high (AC:H) as it requires specific conditions during restoration, and the scope is changed (S:C) because the exploit impacts the underlying operating system. This issue is addressed in Weblate 5.17.
Affected products
- WeblateOrg weblate < 5.17
Identifiers
- CVE-2026-33435
- GHSA-558g-h753-6m33
- PYSEC-2026-154
Timeline
- 2026-04-15: disclosed
- 2026-04-15: advisory: NVD publication date
- 2026-04-16: patched: GitHub Advisory published and fix confirmed in version 5.17