Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-23535: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in WeblateOrg wlc

0
High
VulnerabilityCVE-2026-23535cvecve-2026-23535cwe-22
Published: Fri Jan 16 2026 (01/16/2026, 19:08:24 UTC)
Source: CVE Database V5
Vendor/Project: WeblateOrg
Product: wlc

Description

wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.2, the multi-translation download could write to an arbitrary location when instructed by a crafted server. This vulnerability is fixed in 1.17.2.

AI-Powered Analysis

AILast updated: 01/16/2026, 19:36:00 UTC

Technical Analysis

CVE-2026-23535 is a path traversal vulnerability classified under CWE-22 affecting the Weblate command-line client (wlc) prior to version 1.17.2. Weblate is a popular open-source platform for continuous localization, and wlc is its CLI client that interacts with Weblate's REST API to facilitate translation downloads. The vulnerability arises in the multi-translation download feature, where the client improperly limits the pathname of files it writes to disk. Specifically, a malicious or compromised Weblate server can craft responses that cause wlc to write files outside the intended directory, potentially anywhere on the filesystem. This arbitrary file write can lead to overwriting critical system or application files, insertion of malicious code, or disruption of system operations. Exploitation requires network-level access to a Weblate server and user interaction to initiate the multi-translation download. The CVSS 3.1 vector indicates network attack vector (AV:N), high attack complexity (AC:H), low privileges required (PR:L), and required user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability affects resources beyond the vulnerable component. The impact on confidentiality, integrity, and availability is high (C:H/I:H/A:H). No known exploits are reported in the wild yet, but the vulnerability is publicly disclosed and fixed in version 1.17.2. Organizations using wlc should consider this a critical threat due to the potential for remote arbitrary file writes leading to code execution or data compromise.

Potential Impact

For European organizations, this vulnerability poses significant risks, especially those relying on Weblate and wlc for localization workflows. The arbitrary file write capability can lead to unauthorized modification or deletion of critical files, potentially resulting in system compromise, data breaches, or service disruption. Confidentiality is at risk if sensitive files are overwritten or replaced with malicious payloads. Integrity is compromised as attackers can alter translation files or other system files, undermining trust in localized content. Availability may be affected if critical system files are corrupted, causing application or system failures. Given the network-based attack vector and low privilege requirement, attackers can exploit this vulnerability remotely if users interact with a malicious Weblate server. This is particularly concerning for organizations with distributed teams or those integrating third-party translation services. The lack of known exploits in the wild suggests a window for proactive mitigation before active exploitation occurs.

Mitigation Recommendations

1. Upgrade the Weblate command-line client (wlc) to version 1.17.2 or later immediately to apply the patch that fixes the path traversal vulnerability. 2. Restrict network access to trusted Weblate servers only, using network segmentation, firewall rules, or VPNs to prevent connections to potentially malicious servers. 3. Implement strict validation and monitoring of file system changes in directories used by wlc to detect unauthorized or suspicious file writes. 4. Educate users about the risks of interacting with untrusted Weblate servers and enforce policies to only use verified translation services. 5. Employ application whitelisting or endpoint protection solutions that can detect or block unauthorized file modifications. 6. Regularly audit and review localization workflows and dependencies to identify and remediate potential security gaps. 7. Consider containerizing or sandboxing the wlc client environment to limit the impact of arbitrary file writes.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-13T18:22:43.982Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696a8fc2b22c7ad868d78299

Added to database: 1/16/2026, 7:21:38 PM

Last enriched: 1/16/2026, 7:36:00 PM

Last updated: 1/16/2026, 8:39:29 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats