SSRF (Server-Side Request Forgery) in weblate (CVE-2026-50127)
Summary
SSRF in weblate (CVE-2026-50127). Confidential information can be exposed externally. Exploitable via VCS_RESTRICT_PRIVATE. Mitigation: upgrade to 2026.6 or later.
Original description
The description as published by the source.
Weblate is a web based localization tool. From version 5.15 to before version 2026.6, Weblate's VCS_RESTRICT_PRIVATE did not properly account for some transitional IPv6 ranges, multicast addresses, or some semi-private IPv4 ranges, which allowed some addresses to bypass private range restrictions. This issue has been patched in version 2026.6.
Source: NIST National Vulnerability Database 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-50127 has been found in weblate.
Attackers can target a specific entry point like VCS_RESTRICT_PRIVATE over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade weblate to 2026.6 or later.
If unsure, ask your IT team or search "weblate CVE-2026-50127" on the vendor's site.
CVE-2026-50127 (weblate) — CWE-918 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: VCS_RESTRICT_PRIVATE
Patched: 2026.6 — apply immediately
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.
SSRF (CWE-918) exists in weblate. Attackers reach the vulnerable code path via VCS_RESTRICT_PRIVATE without authentication.
Check the vendor advisory for the affected versions of weblate. Attack surface: VCS_RESTRICT_PRIVATE.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 2026.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade weblate to 2026.6ステージング環境で 2026.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- web github.com
- web github.com