Categories
CVE-2026-24126

Vulnerability in weblate (CVE-2026-24126)

Summary

Vulnerability in weblate (CVE-2026-24126). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.16.0 or later.

Original description

The description as published by the source.

Impact

The SSH management console did not validate the passed input while adding the SSH host key, which could lead to an argument injection to ssh-add.

Patches

Workarounds

Properly limit access to the management console.

References

This issue was reported to us by alexb_616 via HackerOne.

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-24126 has been found in weblate.
Risk of unauthorized operations or information disclosure.
What to do: upgrade weblate to 5.16.0 or later.
If unsure, ask your IT team or search "weblate CVE-2026-24126" on the vendor's site.

CVE-2026-24126 (weblate) — CWE-88
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.16.0 — apply immediately
Workaround: Properly limit access to the management console.
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

A vulnerability (CWE-88) exists in weblate.

📍 Affected scope

Check the vendor advisory for the affected versions of weblate.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.16.0.

🛡️ Workaround

Workaround: Properly limit access to the management console.

🔍 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

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. 2
    Apply temporary workaround mitigate
    Properly limit access to the management console.

    パッチが適用されるまでの応急処置として、Properly limit access to the management console. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade weblate to 5.16.0

    ステージング環境で 5.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

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

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details