Information Disclosure in weblate (CVE-2026-34244)
Summary
Vulnerability in weblate (CVE-2026-34244). Risk of unauthorized operations or information disclosure. Exploitable via project.edit. Mitigation: upgrade to 5.17 or later.
Original description
The description as published by the source.
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 WEBLATE_MACHINERY setting can avoid this.
References
Thanks to @DavidCarliez for disclosing this via GitHub private vulnerability reporting.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-34244 has been found in weblate.
Attackers can target a specific entry point like project.edit over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade weblate to 5.17 or later.
If unsure, ask your IT team or search "weblate CVE-2026-34244" on the vendor's site.
CVE-2026-34244 (weblate) — CWE-200
Attack vector: remote (network-reachable) / no user interaction
Attack surface: project.edit
Patched: 5.17 — apply immediately
Workaround: Limiting available machinery services via WEBLATE_MACHINERY setting can avoid this.
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.
Information disclosure (CWE-200) exists in weblate. Attackers reach the vulnerable code path via project.edit.
Check the vendor advisory for the affected versions of weblate. Attack surface: project.edit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.17.
Workaround: Limiting available machinery services via WEBLATE_MACHINERY setting can avoid this.
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 available machinery services via WEBLATE_MACHINERY setting can avoid this.パッチが適用されるまでの応急処置として、Limiting available machinery services via WEBLATE_MACHINERY setting can avoid this. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade weblate to 5.17ステージング環境で 5.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com