CVE-2026-62364 wlc may disclose API tokens to project-configured URLs

Low 2.3 Published Updated

An attacker can steal API tokens by placing malicious configuration files in a directory where the Weblate CLI is executed.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-62364?

CVE-2026-62364 is a low-severity vulnerability in WeblateOrg wlc, published on 22 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

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

Weakness: CWE-349, CWE-200

Which versions are affected by CVE-2026-62364?

3 open source packages ship an affected version, including wlc.

PackageAffectedFixed in
wlc PyPIAll versions2.0.1
wlc PyPIAll versions2.0.1
wlc PyPIAll versions2.0.1

How do I fix CVE-2026-62364?

Upgrade wlc to 2.0.1 or later.

Is CVE-2026-62364 being exploited?

There is no known exploitation of CVE-2026-62364 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2026-62364, GHSA-3mqq-hv9c-85hc, PYSEC-2026-4180, UBUNTU-CVE-2026-62364.

Is CVE-2026-62364 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free