Back to CVE records
Low 2.3Published Sep 22, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects WeblateOrg wlc. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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
2.3 LOW (v3.1, CNA)CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N
Weakness (CWE)
CWE-200, CWE-349
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Awaiting Analysis
Record last updated
Sep 26, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
WeblateOrg wlc
weblateorg:wlc (from the name)
before 2.0.1
CNA record

References

  • x-refsource-confirm
  • x-refsource-misc
  • x-refsource-misc
  • x-refsource-misc

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.