Quick answers
- Is CVE-2026-33212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33212 being exploited in the wild.
- How severe is CVE-2026-33212?
- Low severity, with a CVSS score of 3.1, 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-33212?
- 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-33212 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-33212?
- 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
An improper access control vulnerability (CWE-284) exists in the Weblate API for tasks. The affected component fails to verify if the requesting user has the appropriate scope or permissions to access logs of in-progress (pending) operations. An attacker with network access and low-level authenticated privileges could potentially view these logs. However, exploitation is hindered by the requirement to guess a random UUID associated with the task, which is further mitigated by default API rate limits. The issue is resolved in version 5.17.
Affected products
- WeblateOrg weblate < 5.17
Identifiers
- CVE-2026-33212
- GHSA-vj45-x3pj-f4w4
- PYSEC-2026-2311
Timeline
- 2026-04-15: patched: Version 5.17 released
- 2026-04-16: advisory