weblate: Relative Path Traversal
CVE-2026-33435 is a high-severity relative path traversal vulnerability in weblate from WeblateOrg, with a CVSS 3.1 base score of 8.0 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected weblate versions: < 5.17. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.72% chance of exploitation within 30 days, higher than 55% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of weblate you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WeblateOrg | weblate | < 5.17 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (github.com).
Official description
Weblate is a web based localization tool. In versions prior to 5.17, the project backup didn't filter Git and Mercurial configuration files which could lead to remote code execution under certain circumstances. This issue has been fixed in version 5.17. If developers are unable to update immediately, they can limit the scope of the vulnerability by restricting access to the project backup, as it is only accessible to users who can create projects.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Relative Path Traversal
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as.. that can resolve to a location that is outside of that directory.
How developers prevent this class of flaw
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/WeblateOrg/weblate/security/advisories/GHSA-558g-h753-6m33Third Party Advisory
Patches and release notes
- github.com/WeblateOrg/weblate/pull/18549Issue Tracking
Other vulnerabilities in weblate
- 8.5 High severity
- 7.7 High severity
- 8.1 High severity
- 8.1 High severity
- 8.8 High severity
- 7.7 High severity
Recent Relative Path Traversal vulnerabilities
- 7.5 High severity
- 8.3 High severity
- 7.5 High severity
- 10.0 Critical severity
- 7.5 High severity
- 9.9 Critical severity
Spotted an error? Tell us.