CVE-2026-23535

line · line Multiple Products

A high-severity vulnerability has been identified in the Line Weblate command-line client (wlc), a tool used for interacting with Weblate's REST API.

Executive summary

A high-severity vulnerability has been identified in the Line Weblate command-line client (wlc), a tool used for interacting with Weblate's REST API. This flaw could allow a remote attacker to execute arbitrary code on the system running the client, potentially leading to a full system compromise, data theft, or disruption of software development pipelines. Organizations are urged to apply vendor patches immediately to mitigate this significant risk.

Vulnerability

The vulnerability exists within the wlc command-line client due to improper sanitization of data received from the Weblate REST API. An attacker who can control the API response (e.g., through a compromised Weblate server or a man-in-the-middle attack) can inject malicious commands. When the wlc client processes this crafted response, it executes the embedded commands with the privileges of the user running the client, leading to remote code execution.

Business impact

This vulnerability is rated as High severity with a CVSS score of 8. Exploitation could have a severe impact on business operations. If the wlc client is used on developer workstations or within CI/CD pipelines, an attacker could steal source code, intellectual property, and access credentials. Furthermore, a successful attack could allow a threat actor to inject malicious code into the software supply chain, pivot to other critical systems on the network, and cause significant operational disruption and reputational damage.

Remediation

Immediate Action: Apply vendor security updates immediately to all systems with the affected wlc client installed. Prioritize patching on critical assets such as CI/CD build servers and developer workstations. After patching, review system and access logs for any signs of compromise that may have occurred before the patch was applied.

Proactive Monitoring: Security teams should monitor for indicators of compromise, including:

  • Logs: Scrutinize system logs on affected machines for unusual process execution, especially child processes spawned by wlc.
  • Network Traffic: Monitor outbound network connections from systems running wlc for traffic to unknown or suspicious IP addresses.
  • System Behavior: Utilize Endpoint Detection and Response (EDR) tools to detect anomalous command-line arguments or script execution originating from the client.

Compensating Controls: If immediate patching is not feasible, implement the following controls to reduce risk:

  • Restrict network access from hosts running wlc, allowing connections only to trusted and verified Weblate API endpoints.
  • Run the wlc client in a sandboxed or containerized environment to limit the impact of a potential compromise.
  • Implement application whitelisting to prevent wlc from executing unauthorized commands or processes.

Exploitation status

Public Exploit Available: false

Analyst recommendation

Due to the high CVSS score of 8.0 and the risk of remote code execution, this vulnerability poses a significant threat to the organization. While this vulnerability is not currently listed on the CISA KEV catalog, its potential impact on developer environments and the software supply chain warrants immediate and decisive action. Organizations are strongly advised to prioritize the immediate application of vendor-supplied patches to all affected systems to prevent potential compromise.