Is CVE-2026-56750 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56750 being exploited in the wild.

How severe is CVE-2026-56750?

Critical severity, with a CVSS score of 4, published 21 July 2026.

Which products and versions are affected?

Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.

Is there a fix for CVE-2026-56750?

Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56750 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-56750?

Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56750: Gitea insufficient session expiration in Remember-Me auth token

Q: Which products and versions are affected?

Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.

Q: Is there a fix for CVE-2026-56750?

Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-56750 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-56750?

Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56750 · Severity: critical · CVSS 4 · Published 2026-07-21

Gitea, a popular self-hosted Git service, contains a flaw in how it handles 'Remember-Me' login sessions. If an attacker steals a user's login token, they can maintain permanent access to the victim's account even after the theft is detected by the system. This allows an attacker to bypass security controls and persistently access private code repositories and user data.

Technologies: Gitea, code.gitea.io/gitea (Go), gitea.dev (Go). Vendors: Gitea, Go.

Quick answers

Is CVE-2026-56750 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56750 being exploited in the wild.
How severe is CVE-2026-56750?: Critical severity, with a CVSS score of 4, published 21 July 2026.
Which products and versions are affected?: Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.
Is there a fix for CVE-2026-56750?: Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56750 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56750?: Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

code.gitea.io/gitea (Go): upgrade to 1.27.0 or later
```
go get code.gitea.io/gitea@v1.27.0
```
gitea.dev (Go): upgrade to 1.27.0 or later
```
go get gitea.dev@v1.27.0
```

Technical details

Gitea implements a split-token (ID:Hash) design for 'Remember-Me' cookies. When a token is used, the hash is rotated while the ID remains constant. If an attacker uses a stolen token, they receive a new rotated hash. When the legitimate user subsequently attempts to use their now-outdated token, Gitea's CheckAuthToken function correctly identifies a hash mismatch but only returns an error (ErrAuthTokenInvalidHash) without deleting the compromised token from the database. This failure to invalidate all sessions associated with the compromised ID allows the attacker's active session to persist indefinitely. The issue is fixed in version 1.27.0.

Affected products

Gitea Gitea < 1.27.0

Identifiers

CVE-2026-56750
GHSA-rgv6-xp99-6mgj
GO-2026-6072

Timeline

2026-07-13: disclosed: Initial report to Gitea
2026-07-21: advisory: GitHub Advisory published
2026-07-21: patched: Fix released in version 1.27.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.