CVE-2026-62364
wlc may disclose API tokens to project-configured URLs
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.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- High
- User interaction
- Required
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
wlc may disclose API tokens to project-configured URLs
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.
- Record
CVE-2026-62364- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Weakness
- CWE-200, CWE-349
- Updated
- 2026-11-02
EUVDEUVD-2026-84823
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.
- Record
EUVD-2026-84823- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-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_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.
- Record
GHSA-3mqq-hv9c-85hc- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Weakness
- CWE-200, CWE-349
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2026-62364- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Weakness
- CWE-200, CWE-349
- Updated
- 2026-11-02
OSV
wlc may disclose API tokens to project-configured URLs
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.
- Record
CVE-2026-62364- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Weakness
- CWE-200, CWE-349
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-62364
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.
- Record
DEBIAN-CVE-2026-62364- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Updated
- 2026-11-02
OSVGHSA-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_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.
- Record
GHSA-3mqq-hv9c-85hc- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Weakness
- CWE-200, CWE-349
- Updated
- 2026-11-02
OSVPYSEC-2026-4180
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_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.
- Record
PYSEC-2026-4180- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-62364
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.
- Record
UBUNTU-CVE-2026-62364- CVSS 3.1
- 2.3 Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
wlcPyPI |
before 2.0.1 | 2.0.1 |
wlcDebian:12 |
All versions, plus listed versions 1.13-21.14-11.15-11.15-21.16.1-11.17.2-12.0.0-12.2.1-1 |
None known |
wlcDebian:13 |
All versions, plus listed versions 1.15-11.15-21.16.1-11.17.2-12.0.0-12.2.1-1 |
None known |
wlcDebian:14 |
before 2.2.1-1, plus listed versions 1.15-11.15-21.16.1-11.17.2-12.0.0-1 |
2.2.1-1 |
wlcPyPI |
before 2.0.1, plus listed versions 0.00.10.100.20.3 Show 27 moreShow less0.40.50.60.70.80.91.01.11.101.111.121.131.141.151.16.11.17.01.17.11.17.21.21.31.41.51.61.71.81.92.0.0 |
2.0.1 |
wlcUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 0.8-10.8-1ubuntu0.1~esm1 |
None known |
wlcUbuntu:Pro:20.04:LTS |
All versions, plus listed versions 1.1-11.2-11.2-1ubuntu0.20.04.1~esm1 |
None known |
wlcUbuntu:Pro:22.04:LTS |
All versions, plus listed versions 1.2-11.2-1ubuntu0.22.04.1~esm1 |
None known |
wlcUbuntu:Pro:24.04:LTS |
All versions, plus listed versions 1.13-21.13-2ubuntu0.1~esm1 |
None known |
wlcUbuntu:26.10 |
All versions, plus listed versions 1.16.1-12.0.0-1 |
None known |
wlcUbuntu:26.04:LTS |
All versions, plus listed versions 1.15-21.16.1-1 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-62364 is a low vulnerability (CVSS 2.3) in Weblateorg Wlc, published September 22, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.08%, the 0th percentile. Fixed in wlc 2.0.1.
References
github.com/WeblateOrg/wlc/security/advisories/GHSA-3mqq-hv9c-85hc