Skip to main content
CVE-2026-22251VulnerabilityPublished

CVE-2026-22251: WeblateOrg wlc · Information Exposure

Affects WeblateOrg wlcSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.17.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.17.0
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade wlc and weblateorg/wlc to 1.17.0.

Affected software

ProductAffectedFixed in
WeblateOrgwlcAffected
  • <1.17.0
Fixed in
  • 1.17.0
GitHubweblateorg/wlcpkg:github/weblateorg/wlcOther threatsAffected
  • <1.17.0
Fixed in
  • 1.17.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade wlc to version 1.17.0 or later, where support for unscoped API keys has been removed. Audit all API keys used with wlc to ensure they are scoped with the minimum necessary permissions, avoiding broad or unscoped keys. Implement strict access controls and rotate API keys regularly to limit exposure duration. Educate users on the risks of using unscoped keys and the importance of following secure key management practices. Monitor network traffic and API usage logs for unusual or unauthorized access patterns that could indicate key leakage or misuse. Employ endpoint security measures to reduce the risk of local compromise and enforce least privilege principles for users operating wlc. Where possible, isolate localization workflows and restrict the environments in which wlc is used to minimize exposure. Finally, maintain up-to-date inventories of software versions and dependencies to quickly identify and remediate vulnerable instances.

Description

wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.0, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be leaked to different servers.

References

Community reviews

Loading reviews…