CVE-2026-62364 WeblateOrg CVE debrief

Who should care

Defenders who use the Weblate command-line client (wlc) in their environments, especially in contexts where the client is used in untrusted repositories or directories, should be aware of this vulnerability and take steps to verify and mitigate it.

Why it matters

CVE-2026-62364 is a vulnerability in the Weblate command-line client (wlc) that can lead to the disclosure of an unscoped API token when used in an untrusted repository or directory. Defenders should prioritize verifying the configuration and usage of wlc in their environments, especially in contexts where the client is used in untrusted repositories or directories.

• Defenders need to verify the configuration and usage of wlc in their environments to prevent potential API token disclosure.
• The vulnerability can be mitigated by updating wlc to version 2.0.1 or later.
• Defenders should review the usage of wlc in their environment and consider implementing additional security measures, such as scoped API tokens and strict configuration controls.

Technical summary

The Weblate command-line client (wlc) is vulnerable to an issue where an unscoped API token can be disclosed when used in an untrusted repository or directory. This occurs because the client's configuration discovery feature can select an API URL from certain configuration files without requiring a matching URL for the provided API token. The issue arises from the client's configuration discovery feature, which can select an API URL from certain configuration files without requiring a matching URL for the provided API token. This can result in the token being sent to an attacker-controlled URL. Defenders should prioritize verifying the configuration and usage of wlc in their environments, especially in contexts

Defensive priority

Defenders should prioritize verifying the configuration and usage of wlc in their environments, especially in contexts where the client is used in untrusted repositories or directories.

Recommended defensive actions

• Verify the configuration of wlc in your environment to ensure that it is not using unscoped API tokens in untrusted repositories or directories.
• Update wlc to version 2.0.1 or later to fix the issue.
• Review the usage of wlc in your environment and consider implementing additional security measures, such as scoped API tokens and strict configuration controls.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, including its description, CVSS score, and affected versions. However, the scope of affected configurations and the exact impact require further verification.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.