Cross-Site Scripting (XSS) in weblate (CVE-2026-44264)
Summary
Cross-site scripting in weblate (CVE-2026-44264). Risk of unauthorized operations or information disclosure. 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, the Markdown renderer used in user comments and other user-provided content didn't properly sanitize some attributes. 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-44264 has been found in weblate.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade weblate to 5.17.1 or later.
If unsure, ask your IT team or search "weblate CVE-2026-44264" on the vendor's site.
CVE-2026-44264 (weblate) — CWE-79 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.17.1 — apply immediately
Workaround: Even though the attacker might be able to inject code into the HTML, the Weblate's strict CSP should mitigate the risks.
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.
Cross-site scripting (XSS) (CWE-79) exists in weblate.
Check the vendor advisory for the affected versions of weblate.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 5.17.1.
Workaround: Even though the attacker might be able to inject code into the HTML, the Weblate's strict CSP should mitigate the risks.
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
Even though the attacker might be able to inject code into the HTML, the Weblate's strict CSP should mitigate the risks.パッチが適用されるまでの応急処置として、Even though the attacker might be able to inject code into the HTML, the Weblate's strict CSP should mitigate the risks. を実施。回避策の副作用 (機能低下) を確認した上で。
-
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
- web github.com
- web github.com