Quick answers
- Is CVE-2026-62364 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62364 being exploited in the wild.
- How severe is CVE-2026-62364?
- Low severity, with a CVSS score of 3.1, published 22 September 2026.
- Which products and versions are affected?
- wlc (PyPI) < 2.0.1, ECOSYSTEM:introduced=0,fixed=2.0.1.
- Is there a fix for CVE-2026-62364?
- Yes. wlc (PyPI): upgrade to 2.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62364 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-62364?
- Check whether you run wlc (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- wlc (PyPI): upgrade to 2.0.1 or later
pip install "wlc>=2.0.1"
Technical details
The vulnerability is a credential exposure issue (CWE-200, CWE-349) in wlc's configuration handling. When an unscoped API token is supplied via WLC_KEY environment variable or --key flag without an explicit URL, wlc automatically discovers and uses the API URL from project configuration files (.weblate, .weblate.ini, or weblate.ini). An attacker who controls these configuration files in a shared repository can redirect the token to their own server. The attack requires the user to be running wlc with secrets in untrusted checkouts. The fix, released in wlc 2.0.1, enforces that WLC_KEY and --key require explicit URL specification (WLC_URL or --url), while preserving support for URL-scoped keys in configuration file sections.
Affected products
- Weblate wlc < 2.0.1
Identifiers
- CVE-2026-62364
- GHSA-3mqq-hv9c-85hc
- PYSEC-2026-4180
Timeline
- 2026-06-26: disclosed: Vulnerability published to GitHub Advisory Database
- 2026-06-26: patched: Fix released in wlc 2.0.1
- 2026-09-22: advisory: Advisory updated on GitHub with CVE-2026-62364