CVE-2026-33220

CVE-2026-33220 is a medium-severity path traversal vulnerability in weblate (pip), affecting versions < 5.17. It is fixed in 5.17.

Summary

Workarounds

The CDN add-on is not enabled by default.

References

Thanks to @spbavarva for reporting this responsibly via GitHub.

Impact

The translation memory API exposed unintended endpoints, which in turn didn't do proper access control.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-33220 has a CVSS score of 6.8 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.17); upgrading removes the vulnerable code path.

Affected versions

weblate (< 5.17)

Security releases

weblate → 5.17 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Frequently Asked Questions

  1. What is CVE-2026-33220? CVE-2026-33220 is a medium-severity path traversal vulnerability in weblate (pip), affecting versions < 5.17. It is fixed in 5.17. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. How severe is CVE-2026-33220? CVE-2026-33220 has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of weblate are affected by CVE-2026-33220? weblate (pip) versions < 5.17 is affected.
  4. Is there a fix for CVE-2026-33220? Yes. CVE-2026-33220 is fixed in 5.17. Upgrade to this version or later.
  5. Is CVE-2026-33220 exploitable, and should I be worried? Whether CVE-2026-33220 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-33220 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-33220? Upgrade weblate to 5.17 or later.

Other vulnerabilities in weblate

CVE-2025-66407CVE-2026-45106CVE-2026-44264CVE-2026-44263CVE-2026-41654

Stop the waste.
Protect your environment with Kodem.