Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

cve-program · severity unknownEUVD CVSS 3.1 9.1 CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 9.1 CRITICALCVSS_V4 Publisher rating CRITICALFixed by code.gitea.io/gitea 1.27.0osv · severity unknownFixed by gitea.dev 1.27.0KEV status unknown

cve-program · CVE-2026-56750

Published

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

Read the publisher's advisory

euvd · EUVD-2026-58145

Published

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

Read the publisher's advisory

nvd · CVE-2026-56750

Published

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

Read the publisher's advisory

osv · GHSA-rgv6-xp99-6mgj

Published

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

osv · GO-2026-6072

Published

Gitea Remember-Me Token Theft Not Invalidating Attacker Session in gitea.dev

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

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

Which CVEs have scores here?

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.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

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%).

Advisory history

16 saved versions

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.

How advisory history works

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.

20 Nov 2026 12:09:58 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

18 Nov 2026 11:24:24 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

16 Nov 2026 09:32:20 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

14 Nov 2026 07:08:23 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

11 Nov 2026 14:07:08 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

9 Nov 2026 13:14:38 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

7 Nov 2026 12:36:48 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

5 Nov 2026 11:49:30 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

3 Nov 2026 11:09:06 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

1 Nov 2026 10:15:23 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

30 Oct 2026 09:59:40 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

28 Oct 2026 08:15:58 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

euvd · EUVD-2026-58145 · Published

25 Oct 2026 14:19:10 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

nvd · CVE-2026-56750 · Published

24 Oct 2026 13:19:41 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

osv · GHSA-rgv6-xp99-6mgj · Published

24 Oct 2026 13:19:41 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session in gitea.dev

osv · GO-2026-6072 · Published

23 Oct 2026 15:48:27 UTC

Gitea Remember-Me Token Theft Not Invalidating Attacker Session

cve-program · CVE-2026-56750 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 21 Nov 00:19 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current