Persistent API access via unrevoked password-change tokens
Published May 7, 2026 · Updated May 7, 2026
Insufficient token expiration in Weblate before 5.17.1 allows remote authenticated users to retain API access after a password change. Password-change handling calls cycle_session_keys() for browser sessions but leaves the user's wlu_* DRF token row in authtoken_token untouched. Exploitation requires a previously obtained personal API token, which remains usable with the associated account's permissions after the password changes.
Summary
What happened
Insufficient token expiration in Weblate before 5.17.1 allows remote authenticated users to retain API access after a password change. Password-change handling calls cycle_session_keys() for browser sessions but leaves the user's wlu_* DRF token row in authtoken_token untouched. Exploitation requires a previously obtained personal API token, which remains usable with the associated account's permissions after the password changes.
The record
- CVE
- CVE-2026-41519
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- Weblate
- Product
- Weblate
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.17.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo