Gitea Remember-Me Token Theft Not Invalidating Attacker Session
euvd · EUVD-2026-58145 · Published
No access to your tenant or devices. Every item links to its source. What this means
Gitea Remember-Me Token Theft Not Invalidating Attacker Session
Read the publisher's advisoryGitea Remember-Me Token Theft Not Invalidating Attacker Session
Read the publisher's advisoryGitea Remember-Me Token Theft Not Invalidating Attacker Session
Read the publisher's advisoryThe vulnerability is in the Remember-Me (gitea_incredible) 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/auth_token.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](https://github.com/go-gitea/gitea/blob/689ace1ce28fd74244b8aa335d9928cdbf6b22f9/services/auth/auth_token.go#L21). When a token is used, its Hash is rotated, but the ID remains the same. If an attacker steals a user's Remember-Me token and uses it to authenticate, the attacker is issued a new rotated token (same ID, new Hash). When the legitimate user later attempts to use their original token, Gitea correctly detects a hash mismatch for the given ID. According to the referenced Paragonie specification, this indicates a compromised token, and ALL active remember-me sessions for that user MUST be invalidated. However, Gitea's `CheckAuthToken` function simply returns `ErrAuthTokenInvalidHash`. The calling code (`autoSignIn`) catches this error and deletes the victim's local cookie via `ctx.DeleteSiteCookie`, but fails to delete the compromised token from the database. As a result, the attacker's active session is never invalidated, and the attacker maintains persistent, indefinite access to the victim's account, entirely defeating the purpose of the split-token security design.
Read the publisher's advisoryGitea Remember-Me Token Theft Not Invalidating Attacker Session in gitea.dev
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
euvd · EUVD-2026-58145 · Published
nvd · CVE-2026-56750 · Published
osv · GHSA-rgv6-xp99-6mgj · Published
osv · GO-2026-6072 · Published
cve-program · CVE-2026-56750 · Published