CVE-2026-41654

Description

### 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.bulk_create([component])[0]`, which bypasses Django's `full_clean()` and therefore never runs the `validate_repo_url` validator. The URL is subsequently written verbatim into `.git/config` by `configure_repo(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.

How to fix CVE-2026-41654

To remediate CVE-2026-41654, upgrade the affected package to a fixed version below.

• —upgrade to 5.17.1 or later

Is CVE-2026-41654 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 5.17.1

CVSS scores

References (8)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-41654
• PATCHgithub.com/WeblateOrg/weblate
• WEBgithub.com/WeblateOrg/weblate/commit/e1eff1f517c1ee315d69581910baaabb724e5ef0
• WEBgithub.com/WeblateOrg/weblate/commit/e4b67a76d95d5165ecb9937f7485fd79223b7f14