Vulnerability in weblate (CVE-2026-41654)
Summary
Vulnerability in weblate (CVE-2026-41654). Confidential information can be exposed externally. Exploitable via project.add. Mitigation: upgrade to 5.17.1 or later.
Original description
The description as published by the source.
Weblate is a web based localization tool. Prior to version 5.17.1, 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/.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). This issue has been patched in version 5.17.1.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41654 has been found in weblate.
Attackers can target a specific entry point like project.add over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade weblate to 5.17.1 or later.
If unsure, ask your IT team or search "weblate CVE-2026-41654" on the vendor's site.
CVE-2026-41654 (weblate) — CWE-20 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: project.add / repo / validate_repo_url
Patched: 5.17.1 — apply immediately
Workaround: Limiting who can create projects limits the scope.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in weblate. Attackers reach the vulnerable code path via project.add.
Check the vendor advisory for the affected versions of weblate. Attack surface: project.add / repo / validate_repo_url.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 5.17.1.
Workaround: Limiting who can create projects limits the scope.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'weblate' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'weblate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
weblateを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Limiting who can create projects limits the scope.パッチが適用されるまでの応急処置として、Limiting who can create projects limits the scope. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade weblate to 5.17.1ステージング環境で 5.17.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com