Security Digest · Vulnerability record
CVE-2026-56750: Gitea Remember-Me Token Theft Not Invalidating Attacker Session
Gitea Remember-Me Token Theft Not Invalidating Attacker Session
CVSS 9.1 Critical EPSS 0.5% · p40
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.5%, percentile 40: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 40% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
code.gitea.io/gitea(Go) < 1.27.0, fixed in 1.27.0. Check your lockfile, including transitive dependencies.
What it is
Gitea Remember-Me Token Theft Not Invalidating Attacker Session
From the GitHub advisory
The vulnerability is in the Remember-Me (giteaincredible) token validation logic, specifically when handling a compromised token (hash mismatch).
The vulnerable function is this one:
https://github.com/go-gitea/gitea/blob/689ace1ce28fd74244b8aa335d9928cdbf6b22f9/services/auth/authtoken.go#L33-L64
Affected Endpoint POST /user/login (and any endpoint triggering autoSignIn via the Remember-Me cookie).
Description Gitea implements Remember-Me cookies using a split token design (ID:Hash), citing the Paragonie secure remember-me guide. When a token is used, its Hash is rotated, but the ID remains the same.
Weakness type: CWE-284, CWE-613.
Product: code.gitea.io/gitea (Go) · Assigned by: Gitea · Published: 2026-08-13
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | code.gitea.io/gitea | < 1.27.0 | 1.27.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Gitea | Gitea Open Source Git Server | <= 1.26.4 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADP | 3.1 | 9.1 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 4.0 | 9.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: present (depends on deployment conditions)
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 0.48% probability of exploitation activity in the next 30 days; percentile 40.
Timeline
- — GitHub-reviewed advisory GHSA-rgv6-xp99-6mgj published (critical)
- — CVE record published by Gitea
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
- GitHub Security Advisory github.com
- Gitea v1.27.0 Release github.com
- Gitea v1.27.0 Release Blog Post blog.gitea.com
Vulnerability records
- GitHub Advisory GHSA-rgv6-xp99-6mgj github.com
- CVE.org record CVE-2026-56750 cve.org
- NVD entry CVE-2026-56750 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com