Information Disclosure in wlc (CVE-2026-62364)
Summary
Vulnerability in wlc (CVE-2026-62364). Risk of unauthorized operations or information disclosure. Exploitable via weblate.ini. Mitigation: upgrade to 2.0.1 or later.
Original description
The description as published by the source.
Impact
wlc could send an unscoped API token to an unintended server when run inside a directory tree containing attacker-controlled project configuration.
If .weblate, .weblate.ini, or weblate.ini defines an API url, and the user supplies a token with WLC_KEY or --key without also pinning the URL, wlc would send the token to the project-configured URL.
Impacted users are those running wlc in untrusted repositories, pull request checkouts, or directories with untrusted ancestor configuration while using WLC_KEY or --key.
Patches
The issue is patched in wlc 2.0.1 via https://github.com/WeblateOrg/wlc/pull/1500.
The fix rejects unscoped keys when the API URL comes from automatically discovered project configuration:
WLC_KEYnow requiresWLC_URL.--keynow requires--url.- URL-scoped keys in the
[keys]configuration section remain supported.
Users should upgrade to wlc 2.0.1 or newer.
Workarounds
Without upgrading, users can avoid the issue by explicitly pinning the API URL whenever using an unscoped key:
WLC_URL=https://hosted.weblate.org/api/ WLC_KEY=... wlc ...
or:
wlc --url https://hosted.weblate.org/api/ --key ... ...
Alternatively, use URL-scoped keys in the [keys] section instead of WLC_KEY or --key, and avoid running wlc with secrets in untrusted checkouts.
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-62364 has been found in wlc.
Attackers can target a specific entry point like weblate.ini over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 2.3/10.
What to do: upgrade wlc to 2.0.1 or later.
If unsure, ask your IT team or search "wlc CVE-2026-62364" on the vendor's site.
CVE-2026-62364 (wlc) — CWE-200 / CVSS v3 2.3
Attack vector: local
Attack surface: weblate.ini / WLC_KEY / WLC_URL
Patched: 2.0.1 — 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.
Information disclosure (CWE-200) exists in wlc. Attackers reach the vulnerable code path via weblate.ini.
Check the vendor advisory for the affected versions of wlc. Attack surface: weblate.ini / WLC_KEY / WLC_URL.
Severity: Low (CVSS 2.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.0.1.
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 'wlc' . 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 'wlc' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wlcを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade wlc to 2.0.1ステージング環境で 2.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com