Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gitea versions before 1.27.0 are affected. When a stolen Remember-Me token is reused and the legitimate user later presents their original token, Gitea detects the mismatch but does not invalidate the attacker's token, so an attacker who has stolen a Remember-Me token can keep access to the victim's account indefinitely. The source does not describe required attacker conditions beyond holding the stolen token. Upgrade to Gitea 1.27.0 or later.
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 |
|---|---|---|---|---|
| 9.1 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | ADP (CISA-ADP) |
- CISA KEV Not listed.
- EPSS 0.0048, the 41st percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:55 UTC First seen by agentprime
- 31 Oct 2026, 14:55 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rgv6-xp99-6mgj
- OSV: GHSA-rgv6-xp99-6mgj
- github.com/go-gitea/gitea/security/advisories/GHSA-rgv6-xp99-6mgj
- github.com/go-gitea/gitea/pull/38406
- github.com/go-gitea/gitea/pull/38426
- github.com/go-gitea/gitea/commit/de4b8277e9cb576f2315fb03b5ab6478b42a1d31
- github.com/go-gitea/gitea/commit/f69e15afe7496cc62e96dab244629c69eb31a7bf
- github.com/go-gitea/gitea
- github.com/go-gitea/gitea/releases/tag/v1.27.0