Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Weblate versions before 5.17.1 do not revoke a user's API tokens when that user changes their password, although browser sessions are invalidated. An attacker who already holds a valid API token for an account could keep using it after the owner changes the password. Upgrade to Weblate 5.17.1 or later. The source gives few details on how the token would be obtained.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.2 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0027, the 19th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:04 UTC First seen by agentprime
- 31 Oct 2026, 15:04 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-6j8j-4qp3-36p2
- OSV: GHSA-6j8j-4qp3-36p2
- github.com/WeblateOrg/weblate/security/advisories/GHSA-6j8j-4qp3-36p2
- nvd.nist.gov/vuln/detail/CVE-2026-41519
- github.com/WeblateOrg/weblate/pull/19057
- github.com/WeblateOrg/weblate/commit/649a2da81700542f95c0807b3c625fc3bb0eaf95
- github.com/WeblateOrg/weblate
- github.com/WeblateOrg/weblate/releases/tag/weblate-5.17.1