Gitea Remember-Me Token Theft Not Invalidating Attacker Session (CVE-2026-56750)
Gitea versions prior to 1.27.0 contain a vulnerability in the Remember-Me token validation logic. When a Remember-Me token is compromised and used by an attacker, Gitea rotates the token hash but does not invalidate all active sessions for the user as required. This allows the attacker to maintain persistent access to the victim's account despite the legitimate user detecting a token mismatch. The issue arises because the compromised token is not deleted from the database, defeating the security design intended to prevent indefinite unauthorized access.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-56750) affects Gitea's Remember-Me token mechanism, which uses a split token design (ID and Hash). Upon token use, the hash is rotated but the ID remains the same. If an attacker steals a token and authenticates, they receive a new rotated token. When the legitimate user later uses their original token, Gitea detects a hash mismatch indicating compromise. According to the Paragonie specification, all active Remember-Me sessions should then be invalidated. However, Gitea's implementation only deletes the victim's local cookie and does not remove the compromised token from the database, allowing the attacker to retain persistent access indefinitely. This flaw is present in versions before 1.27.0.
Potential Impact
An attacker who steals a user's Remember-Me token can maintain persistent, indefinite access to the victim's account because the compromised token is not invalidated in the backend. This undermines the security model of the Remember-Me feature and allows unauthorized session persistence despite detection of token compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider disabling the Remember-Me feature or monitoring for suspicious session activity. The vendor advisory or repository should be monitored for updates addressing this vulnerability.
Gitea Remember-Me Token Theft Not Invalidating Attacker Session (CVE-2026-56750)
Description
Gitea versions prior to 1.27.0 contain a vulnerability in the Remember-Me token validation logic. When a Remember-Me token is compromised and used by an attacker, Gitea rotates the token hash but does not invalidate all active sessions for the user as required. This allows the attacker to maintain persistent access to the victim's account despite the legitimate user detecting a token mismatch. The issue arises because the compromised token is not deleted from the database, defeating the security design intended to prevent indefinite unauthorized access.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-56750) affects Gitea's Remember-Me token mechanism, which uses a split token design (ID and Hash). Upon token use, the hash is rotated but the ID remains the same. If an attacker steals a token and authenticates, they receive a new rotated token. When the legitimate user later uses their original token, Gitea detects a hash mismatch indicating compromise. According to the Paragonie specification, all active Remember-Me sessions should then be invalidated. However, Gitea's implementation only deletes the victim's local cookie and does not remove the compromised token from the database, allowing the attacker to retain persistent access indefinitely. This flaw is present in versions before 1.27.0.
Potential Impact
An attacker who steals a user's Remember-Me token can maintain persistent, indefinite access to the victim's account because the compromised token is not invalidated in the backend. This undermines the security model of the Remember-Me feature and allows unauthorized session persistence despite detection of token compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider disabling the Remember-Me feature or monitoring for suspicious session activity. The vendor advisory or repository should be monitored for updates addressing this vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rgv6-xp99-6mgj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-56750"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 4.0
Threat ID: 6a600abb9c2644c7f8fe2bad
Added to database: 07/22/2026, 00:11:39 UTC
Last enriched: 07/22/2026, 00:52:43 UTC
Last updated: 07/22/2026, 01:56:13 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.