Quick answers
- Is CVE-2025-58352 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-58352 being exploited in the wild.
- How severe is CVE-2025-58352?
- Medium severity, with a CVSS score of 4, published 7 July 2026.
- Which products and versions are affected?
- weblate (PyPI) ECOSYSTEM:introduced=0,fixed=5.13.1.
- Is there a fix for CVE-2025-58352?
- Yes. weblate (PyPI): upgrade to 5.13.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-58352 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-58352?
- Check whether you run weblate (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
- weblate (PyPI): upgrade to 5.13.1 or later
pip install "weblate>=5.13.1"
Technical details
The vulnerability stems from improper session management during the second factor verification flow (CWE-613). When a user initiates two-factor authentication, the session timeout is set to an overly long duration, which attackers can exploit to circumvent rate limiting protections on authentication attempts. The attack vector is network-based and requires initial authentication (low privilege) plus user interaction (passive). An attacker can leverage this to perform brute-force attacks against two-factor codes without being rate-limited. The vulnerability affects Weblate versions prior to 5.13.1, which addressed the issue via pull request #16002 by reducing the session expiry time during second factor verification.
Affected products
- Weblate Weblate all versions before 5.13.1
Identifiers
- CVE-2025-58352
- GHSA-377j-wj38-4728
- PYSEC-2026-2036
Timeline
- 2025-09-04: disclosed: Advisory published
- 2025-09-04: patched: Fixed in version 5.13.1