Vulnerability in weblate (CVE-2026-33212)
Summary
Vulnerability in weblate (CVE-2026-33212). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.17 or later.
Original description
The description as published by the source.
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
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ř.
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-33212 has been found in weblate.
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-33212" on the vendor's site.
CVE-2026-33212 (weblate) — CWE-284
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.17 — apply immediately
Workaround: The attacker needs to guess the random UUID of the task, so exploiting this is unlikely with the default API rate limits.
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-284) exists in weblate.
Check the vendor advisory for the affected versions of weblate.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.17.
Workaround: The attacker needs to guess the random UUID of the task, so exploiting this is unlikely with the default API rate limits.
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
The attacker needs to guess the random UUID of the task, so exploiting this is unlikely with the default API rate limits.パッチが適用されるまでの応急処置として、The attacker needs to guess the random UUID of the task, so exploiting this is unlikely with the default API rate limits. を実施。回避策の副作用 (機能低下) を確認した上で。
-
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