Advisory record · GHSA-rgv6-xp99-6mgj

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

CVSS 9.1 CriticalCriticalEPSS 0.0048 · 41st percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 21 Jul 2026, 20:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
code.gitea.io/giteaGo<1.27.01.27.0
Identifiers
GHSA-rgv6-xp99-6mgj · CVE-2026-56750 · GO-2026-6072
Weakness (CWE)
CWE-284 · CWE-613
Published
21 Jul 2026
Updated
27 Jul 2026

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.

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
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

  1. 31 Oct 2026, 14:55 UTC First seen by agentprime
  2. 31 Oct 2026, 14:55 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.