← Back
CVE-2026-45106 medium CVSS 4.6

Cross-Site Scripting (XSS) in weblate (CVE-2026-45106)

Summary

cross-site scripting in weblate (CVE-2026-45106). Risk of unauthorized operations or information disclosure. Exploitable via ``source``. Mitigation: upgrade to `2026.5` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-45106** has been found in weblate. Attackers can target a specific entry point like ``source`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 4.6/10. What to do: upgrade weblate to **2026.5** or later. If unsure, ask your IT team or search "weblate CVE-2026-45106" on the vendor's site.
CVE-2026-45106 (weblate) — CWE-79 / CVSS v3 4.6 Attack vector: remote (network-reachable) Attack surface: `source` / `context` Patched: `2026.5` — apply immediately Workaround: Only the search preview on the selected views is affected. 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
**Cross-site scripting (XSS)** (CWE-79) exists in weblate. Attackers reach the vulnerable code path via ``source`` without authentication.
📍 Affected scope
weblate — . Attack surface: `source` / `context`.
🔥 Severity
Severity: Medium (CVSS 4.6/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2026.5**.
🛡️ Workaround
Workaround: Only the search preview on the selected views is affected.
🔍 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

  1. 1
    Identify exposure identify
    grep -r 'weblate' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `weblate` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate
    Only the search preview on the selected views is affected.

    パッチが適用されるまでの応急処置として、Only the search preview on the selected views is affected. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade weblate to 2026.5

    ステージング環境で 2026.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip weblate
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.5"}]}]
PyPI weblate
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.5"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →