CVE-2026-62364
When wlc runs in an untrusted repository, pull request checkout, or directory with untrusted ancestor configuration, it can send the token to an attacker-controlled project-configured URL.
Does this matter?
Lower severity and a low EPSS score (0.08%). Track it; it rarely justifies an emergency change on its own.
Description
wlc is a Weblate command-line client using Weblate's REST API. Prior to 2.0.1, automatically discovered configuration from .weblate, .weblate.ini, or weblate.ini can select the API URL while an unscoped API token is supplied through WLC_KEY or --key without a matching WLC_URL or --url. When wlc runs in an untrusted repository, pull request checkout, or directory with untrusted ancestor configuration, it can send the token to an attacker-controlled project-configured URL. URL-scoped keys in [keys] are not affected. This issue is fixed in version 2.0.1.
- CVSS 3.1
- 2.3 LOWCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N
- EPSS
- 0.08% probability · 0th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-200, CWE-349
- Source
- security-advisories@github.com
EPSS moved from 0.1% on 23 September 2026 to 0.1% on 26 October 2026.
References
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.