Quick answers
- Is CVE-2026-39845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39845 being exploited in the wild.
- How severe is CVE-2026-39845?
- Medium severity, with a CVSS score of 4.1, published 15 April 2026.
- Which products and versions are affected?
- weblate (PyPI) < 5.17, ECOSYSTEM:introduced=0,fixed=5.17.
- Is there a fix for CVE-2026-39845?
- Yes. weblate (PyPI): upgrade to 5.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39845 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39845?
- Check whether you run weblate (PyPI) or Weblate 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.17 or later
pip install "weblate>=5.17"
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in Weblate's webhook add-on due to the use of an unprotected fetch_url() function. The component fails to apply existing SSRF protections when processing webhook requests. An attacker with high privileges (PR:H) can exploit this over the network to make the server send requests to arbitrary internal or external URLs. This can lead to unauthorized information disclosure from internal services. The issue is fixed in version 5.17.
Affected products
- WeblateOrg weblate < 5.17
Identifiers
- CVE-2026-39845
- GHSA-f8hv-g549-hwg2
- PYSEC-2026-156
Timeline
- 2026-04-15: disclosed
- 2026-04-16: advisory
- 2026-04-15: patched: Version 5.17 released