← Back
CVE-2026-41654
high
CVSS 8.1
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-20) exists in weblate. Attackers reach the vulnerable code path via ``project.add`` without authentication.
📍 Affected scope
weblate — . Attack surface: `project.add` / `repo` / `validate_repo_url`.
🔥 Severity
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **5.17.1**.
🛡️ Workaround
Workaround: Limiting who can create projects limits the scope.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Limiting who can create projects limits the scope.パッチが適用されるまでの応急処置として、Limiting who can create projects limits the scope. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade weblate to 5.17.1ステージング環境で 5.17.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
weblate
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.1"}]}]
PyPI
weblate
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41654
- package https://github.com/WeblateOrg/weblate
- patch [email protected]
- patch [email protected]
- patch [email protected]
- patch [email protected]
- patch [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-cwcx-382v-8m9g