Gitea Remember-Me Token Theft Not Invalidating Attacker Session
CVE-2026-56750
This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 56(Track)EG Risk 56/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Sep 7, 2026Gitea Remember-Me Token Theft Not Invalidating Attacker Session · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-rgv6-xp99-6mgjVendor Advisories for CVE-2026-56750(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| code.gitea.io/gitea | — | 1.27.0 | — |
| gitea.dev | — | 1.27.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 52× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-11 18:16 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 08:59 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 11:17 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 22:32 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 14:56 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 19:50 UTCEG score recompute
- 2026-09-05 08:30 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 00:56 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:19 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 02:12 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 15:20 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:43 UTCEG score recompute
Show 31 moreShow fewer
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 15:04 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 18:48 UTCEG score recompute
- 2026-08-24 13:00 UTCEG score recompute
- 2026-08-23 04:20 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:51 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 23:02 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 22:31 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 19:28 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 16:57 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 16:43 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:36 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 04:23 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 19:39 UTCEG score recompute▲ 9.10
- 2026-08-14 19:38 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
- 2026-08-13 17:17 UTCNVD update
- 2026-08-13 17:01 UTCMITRE cvelistV5
- 2026-08-01 01:31 UTCEG score recompute
- 2026-07-29 05:43 UTCEG score recompute
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-21 21:21 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-284
Frequently asked(5)
What is CVE-2026-56750?
When was CVE-2026-56750 disclosed?
Is CVE-2026-56750 actively exploited?
What is the CVSS score of CVE-2026-56750?
How do I remediate CVE-2026-56750?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56750
Is Your Infrastructure Affected by CVE-2026-56750?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.