Advisory record · GHSA-6j8j-4qp3-36p2

Weblate Doesn't Invalidate API Token on Password Change

CVSS 4.2 MediumEPSS 0.0027 · 19th percentile

Published by the GitHub Advisory Database at 30 Apr 2026, 17:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
weblatePyPI<5.17.15.17.1
Identifiers
GHSA-6j8j-4qp3-36p2 · CVE-2026-41519 · PYSEC-2026-2316
Weakness (CWE)
CWE-613
Published
30 Apr 2026
Updated
13 Jul 2026

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.

Written 6 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 15:04 UTC First seen by agentprime
  2. 31 Oct 2026, 15:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.