cve.bz

CVE-2026-56750 gitea gitea open source git server: Improper Access Control

9.1 criticalEPSS 0.5%Fix available

Critical (9.1) in gitea gitea open source git server. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in code.gitea.io/gitea 1.27.0.

On this page
Gitea Remember-Me Token Theft Not Invalidating Attacker Session

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-08-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-56750 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56750?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56750?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56750 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Gitea Open Source Git Serverthrough 1.26.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rgv6-xp99-6mgjGocode.gitea.io/gitea<1.27.01.27.0
GO-2026-6072Gogitea.dev<1.27.01.27.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260727T201416-160000.1.1SUSE-SU-2026:23216-1 SUSE-SU-2026:23227-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260727T201416-160000.1.1openSUSE-SU-2026:21551-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

An Important flaw exists in Gitea where the theft of a 'remember-me' token does not invalidate an attacker's session. This allows an attacker to retain unauthorized access to a user's account even after the legitimate user has logged out or changed their password, extending the window of compromise.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
OpenShift Pipelinesopenshift-pipelines-clientAffected
OpenShift Pipelinesopenshift-pipelines/pipelines-cli-tkn-rhel9Will not fix
OpenShift Pipelinesopenshift-pipelines/pipelines-opc-rhel9Will not fix
OpenShift Pipelinesopenshift-pipelines/pipelines-pipelines-as-code-cli-rhel9Will not fix
OpenShift Pipelinesopenshift-pipelines/pipelines-pipelines-as-code-controller-rhel9Will not fix
OpenShift Pipelinesopenshift-pipelines/pipelines-pipelines-as-code-watcher-rhel9Will not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-56750.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON