Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Check if your repositories are affected!View on GitHub
Search

GHSA-3mqq-hv9c-85hc

LowCVSS 2.3 / 10
Published Sep 22, 2026·Last modified Sep 22, 2026
Affected Components(1)
PyPI logowlc
< 2.0.1
Description

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.
  • 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.

  • The issue was independently reported by type5afe and visionx7 using HackerOne.
Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
2.3

The vulnerability requires local access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs high-level or administrative privileges. The attacker needs the user to perform some action, like clicking a link. The vulnerability can affect other systems as well, not just the initial system. There is a low impact on the confidentiality of the information.

Threat Intelligence
2.1

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities
  • CVE-2026-62364
    Alias
  • EUVD-2026-84823
    Alias

Browse More

Low severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard