wlc
Affected
- introduced
0, fixed2.0.1(ecosystem)
Fixed versions
2.0.1
Fix
- Fixed version
2.0.1pip install --upgrade wlc==2.0.1
Advisory
Also known as: CVE-2026-62364, GHSA-3mqq-hv9c-85hc
wlc may disclose API tokens to project-configured URLs
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_KEY now requires WLC_URL.--key now requires --url.[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.
Low Basis: CVSS v3 score 2.3, vector CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N
0, fixed 2.0.1 (ecosystem)2.0.1
2.0.1pip install --upgrade wlc==2.0.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0