WeblateOrg wlc up to 1.16.x REST API information disclosure

Summaryinfo

A vulnerability classified as problematic has been found in WeblateOrg wlc up to 1.16.x. Affected is an unknown function of the component REST API. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2026-22251. The attack must be carried out locally. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in WeblateOrg wlc up to 1.16.x and classified as problematic. This issue affects some unknown processing of the component REST API. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-22251 since 01/07/2026. The exploitation is known to be difficult. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 282618 (Linux Distros Unpatched Vulnerability : CVE-2026-22251), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.17.0 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (282618) and EUVD (EUVD-2026-1919). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• WeblateOrg

Name

• wlc

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16

Website

• Product: https://github.com/WeblateOrg/wlc/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion