CVE-2026-62364

wlc may disclose API tokens to project-configured URLs

LOW
2.3
CVSS Score
Published: September 22, 2026 at 08:17 PM UTC
Updated: September 26, 2026 at 01:17 AM UTC
1 product affected across 1 vendorWlc

Using wlc by WeblateOrg?

Get instant alerts when new vulnerabilities affect wlc - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.3
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.0.1
Affected range stops below 2.0.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2.3LOWGitHub_M
Attack Vector
LOCAL
Complexity
HIGH
Privileges
HIGH
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-200CWE-349

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card