Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
37 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact The API did not properly handle project- and workspace-scoped teams and allowed setting invalid configurations, including granting access to projects the user has no access to. Patches https://github.com/WeblateOrg/weblate/pull/19970 References Parts of this issue were independently reported by four reporters: @H3xV0rT3x via GitHub imhego via HackerOne v01demort via HackerOne b4nder via HackerOne
Recommended action: Upgrade to 2026.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The several endpoints could leak object existence information to users who had no access to it by HTTP status code 403 instead of 404. Patches https://github.com/WeblateOrg/weblate/pull/19971 References Thanks to Yaohui Wang for reporting this via GitHub.
Recommended action: Upgrade to 2026.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Weblate's VCSRESTRICTPRIVATE did not properly account for some transitional IPv6 ranges, multicast addresses, or some semi-private IPv4 ranges, which allowed some addresses to bypass private range restrictions. Patches https://github.com/WeblateOrg/weblate/pull/19768 Resources The issue was reported by @tonghuaroot via GitHub, and the same user also provided the initial patch.
Recommended action: Upgrade to 2026.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The Create Component functionality in Weblate allows authorized users to add new translation components by specifying both a version control system and a source code repository URL to pull from. However, the repository URL field is not validated or sanitized, allowing an attacker to supply arbitrary protocols, hostnames, and IP addresses, including localhost, internal network addresses, and local filenames. When the Mercurial version control system is selected, Weblate exposes the full server-side HTTP response for the provided URL. This effectively creates a server-side request forgery (SSRF) primitive that can probe internal services and return their contents. In addition to accessing internal HTTP endpoints, the behavior also enables local file enumeration by attempting file:// requests. While file contents may not always be returned, the application’s error messages clearly differentiate between files that exist and files that do not, revealing information about the…
Recommended action: Upgrade to 5.15 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Weblate's live search preview renders unit source and context as HTML without escaping. Any contributor whose content reaches those fields stores HTML and CSS that runs inside the authenticated editor of every user who runs a matching search. Patches https://github.com/WeblateOrg/weblate/pull/19422 Workarounds Only the search preview on the selected views is affected. Resources Weblate thanks @adrgs for reporting this issue responsibly via GitHub.
Recommended action: Upgrade to 2026.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The Markdown renderer used in user comments and other user-provided content didn't properly sanitize some attributes. Patches https://github.com/WeblateOrg/weblate/pull/19259 Workarounds Even though the attacker might be able to inject code into the HTML, the Weblate's strict CSP should mitigate the risks. Acknowlegement Michal Čihař has identified and fixed this vulnerability.
Recommended action: Upgrade to 5.17.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The screenshots, tasks, and component link API allowed for the enumeration of translations in a project inaccessible to the user. Patches https://github.com/WeblateOrg/weblate/pull/19258 Acknowledgement Weblate thanks Luay for reporting this vulnerability according to the organization's security issues guideline.
Recommended action: Upgrade to 5.17.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact An authenticated user with project.add permission (default on hosted Weblate SaaS and for any user holding an active billing/trial plan) can import a crafted project backup ZIP whose components/<name.json contains an attacker-chosen repo URL pointing at a private address (e.g. http://127.0.0.1:9999/) or using a non-allow-listed scheme (e.g. file://, git://). Weblate persists the component via Component.objects.bulkcreate([component])[0], which bypasses Django's fullclean() and therefore never runs the validaterepourl validator. The URL is subsequently written verbatim into .git/config by configurerepo(pull=False). Patches https://github.com/WeblateOrg/weblate/pull/19061 https://github.com/WeblateOrg/weblate/pull/19062 Workarounds Limiting who can create projects limits the scope. Resources Weblate thanks @fg0x0 for reporting this vulnerability via GitHub.
Recommended action: Upgrade to 5.17.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact When a user changes their password, browser sessions are correctly invalidated via cyclesessionkeys(), but DRF API tokens (wlu prefix) stored in authtokentoken are not revoked. Patches https://github.com/WeblateOrg/weblate/pull/19057 Resources Weblate thanks Sang Yu Jeon for reporting this via GitHub.
Recommended action: Upgrade to 5.17.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Weblate repository-boundary validation relies on string prefix checks on resolved absolute paths. In multiple code paths, the check uses startswith against the repository root path. This is not path-segment aware and can be bypassed when the external path shares the same string prefix as the repository path (for example, repo and repooutside). Patches https://github.com/WeblateOrg/weblate/pull/18847 References Thanks to m9nx4u for reporting this issue via HackerOne.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The webhook add-on did not utilize existing SSRF protection. Patches https://github.com/WeblateOrg/weblate/pull/18815 Workarounds Disabling the add-on would avoid misusing this. References Thanks to @Lihfdgjr for reporting this via GitHub.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The user patching API endpoint didn't properly limit the scope of edits. Patches https://github.com/WeblateOrg/weblate/pull/18687 References Thanks to @tikket1 and @DavidCarliez for reporting this via GitHub. We received two individual reports for this.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact A user with the project.edit permission (granted by the per-project "Administration" role) can configure machine translation service URLs pointing to arbitrary internal network addresses. During configuration validation, Weblate makes an HTTP request to the attacker-controlled URL and reflects up to 200 characters of the response body back to the user in an error message. This constitutes a Server-Side Request Forgery (SSRF) with partial response read. Patches https://github.com/WeblateOrg/weblate/pull/18684 The solution then has been cleaned up in followup patches Workarounds Limiting available machinery services via WEBLATEMACHINERY setting can avoid this. References Thanks to @DavidCarliez for disclosing this via GitHub private vulnerability reporting.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The ZIP download feature didn't verify downloaded file and it could follow symlinks outside the repository. Patches https://github.com/WeblateOrg/weblate/pull/18683 References Thanks to @DavidCarliez for reporting this vulnerability via GitHub.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The ALLOWEDASSETDOMAINS setting applied only to the first issued requests and didn't restrict possible redirects. Patches https://github.com/WeblateOrg/weblate/pull/18550 References This issue was reported by @spbavarva via GitHub.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The project backup didn't filter Git and Mercurial configuration files and this could lead to remote code execution under certain circumstances. Patches https://github.com/WeblateOrg/weblate/pull/18549 Workarounds The project backup is only accessible to users who can create projects. Restricting access to this limits scope of the vulnerability. References This issue was reported by ggamno via HackerOne.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The translation memory API exposed unintended endpoints, which in turn didn't do proper access control. Patches https://github.com/WeblateOrg/weblate/pull/18516 Workarounds The CDN add-on is not enabled by default. References Thanks to @spbavarva for reporting this responsibly via GitHub.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The translation memory API exposed unintended endpoints, which in turn didn't do proper access control. Patches https://github.com/WeblateOrg/weblate/pull/18513 Workarounds Blocking access to /api/memory/ in the HTTP server removes access to this feature. References This issue was reported by ggamno via HackerOne.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The API for tasks didn't verify user access for pending tasks. This could expose logs of in-progress operations to users who don't have access to given scope. Patches https://github.com/WeblateOrg/weblate/pull/18515 Workarounds The attacker needs to guess the random UUID of the task, so exploiting this is unlikely with the default API rate limits. References This issue was identified by Michal Čihař.
Recommended action: Upgrade to 5.17 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Users were able to obtain add-on configuration via API. Patches https://github.com/WeblateOrg/weblate/pull/18107 https://github.com/WeblateOrg/weblate/pull/18164 References Weblate thanks @lighthousekeeper1212 for responsible disclosure.
Recommended action: Upgrade to 5.16.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The SSH management console did not validate the passed input while adding the SSH host key, which could lead to an argument injection to ssh-add. Patches https://github.com/WeblateOrg/weblate/pull/17722 Workarounds Properly limit access to the management console. References This issue was reported to us by alexb616 via HackerOne.
Recommended action: Upgrade to 5.16.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The screenshot images were served directly by the HTTP server without proper access control. This could allow an unauthenticated user to access screenshots after guessing their filename. Patches https://github.com/WeblateOrg/weblate/pull/17516 References Thanks to Lukas May and Michael Leu for reporting this.
Recommended action: Upgrade to 5.15.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact It was possible to overwrite Git configuration remotely and override some of its behavior. Resources Thanks to Jason Marcello for responsible disclosure.
Recommended action: Upgrade to 5.15.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact It was possible to read arbitrary files from the server file system using crafted symbolic links in the repository. Resources Thanks to Jason Marcello for responsible disclosure.
Recommended action: Upgrade to 5.15.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact It was possible to retrieve user notification settings or list all users via API. Patches https://github.com/WeblateOrg/weblate/pull/17256 References Thanks to Hector Ruiz Ruiz & NaxusAI for responsibly disclosing this vulnerability to Weblate.
Recommended action: Upgrade to 5.15 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.