weblateorg/wlc · Security
Weblate wlc has insecure API key configuration
- GHSA ID
- GHSA-9rp8-h4g8-8766
- CVE ID
- CVE-2026-22251
- Severity
- medium
- Published
- Updated
- CVSS
- 5.3 · CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
- CVSS v3
- 5.3 · CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
Description
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
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.
CWEs
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CWE-922 · Insecure Storage of Sensitive Information
References
- https://github.com/WeblateOrg/wlc/security/advisories/GHSA-9rp8-h4g8-8766 ↗
- https://github.com/WeblateOrg/wlc/pull/1098 ↗
- https://github.com/WeblateOrg/wlc/commit/aafdb507a9e66574ade1f68c50c4fe75dbe80797 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2026-22251 ↗
- https://github.com/advisories/GHSA-9rp8-h4g8-8766 ↗