Skip to main content
VulnerabilityPublished Updated

CVE-2026-41519: Weblate Doesn't Invalidate API Token on Password Change

Affects weblateSource GCVE Database

0
Authoritative record:CVE-2026-41519· Medium 4.2

Not known to be exploited · CVSS 4.2 Medium : upgrade to 5.17.1 when convenient.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.17.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade weblate to 5.17.1.

Affected software

ProductAffectedFixed in
PyPIweblateAffected
  • <5.17.1
Fixed in
  • 5.17.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### Impact When a user changes their password, browser sessions are correctly invalidated via `cycle_session_keys()`, but DRF API tokens (`wlu_*` prefix) stored in `authtoken_token` are not revoked. ### Patches * https://github.com/WeblateOrg/weblate/pull/19057 ### Resources Weblate thanks Sang Yu Jeon for reporting this via GitHub.

References

Community reviews

Loading reviews…