CVE-2026-22251: Weblate wlc has insecure API key configuration
Impact Historically, 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 used against different server. Patches https://github.com/WeblateOrg/wlc/pull/1098 Workarounds Remove unscoped key from wlc configuration. Only use URL-scoped keys in the [keys] sections.
Published Jan 12, 2026
Affected packages
wlc
- Ecosystem
- PyPI
- Affected
- < 1.17.0
- Fixed in
- 1.17.0
- Check
pip show wlc
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Historically, 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 used against different server.
Patches
- https://github.com/WeblateOrg/wlc/pull/1098
Workarounds
Remove unscoped key from wlc configuration. Only use URL-scoped keys in the [keys] sections.
References
This issue was reported to us by wh1zee via HackerOne.
Credited to nijel, 0daysec-xyz.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-62364
wlc may disclose API tokens to project-configured URLs
low2.3Sep 22, 2026CVE-2026-42150
wlc: print_html outputs API data without HTML escaping
medium5.1Apr 24, 2026CVE-2026-23535
Weblate wlc path traversal vulnerability: Unsanitized API slugs in download command
high8.0Jan 16, 2026CVE-2026-22250
Weblate command-line client susceptible to SSL verification skip
low2.5Jan 12, 2026
