Skip to content
Fencer Vulns
medium 5.3

CVE-2026-22251 json

wlc may leak API keys due to an insecure API key configuration

published 2026-01-12 9 mo ago modified 2026-07-07 4 mo ago also GHSA-9rp8-h4g8-8766 , PYSEC-2026-2052 , EUVD-2026-1919

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi wlc 1.17.0
  • weblate wlc 1.17.0
  • wlc Debian 14 1.17.2-1

debian advisories DEBIAN-CVE-2026-22251

  • wlc Ubuntu 25.10 1.15-2ubuntu0.1
  • wlc Ubuntu Pro 18.04 LTS 0.8-1ubuntu0.1~esm1
  • wlc Ubuntu Pro 20.04 LTS 1.2-1ubuntu0.20.04.1~esm1
  • wlc Ubuntu Pro 22.04 LTS 1.2-1ubuntu0.22.04.1~esm1
  • wlc Ubuntu Pro 24.04 LTS 1.13-2ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2026-22251

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi wlc
<1.17.0
1.17.0

Affected products

  • WeblateOrg wlc

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-922 Insecure Storage of Sensitive Information

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.