CVE-2026-26247: Gitea Open Source Git Server · Improper Access Control
Affects Gitea Open Source Git ServerSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.25.5 as a priority.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.25.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Gitea Open Source Git Server and github.com/go-gitea/gitea to 1.25.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GiteaGitea Open Source Git Server | Affected
| Fixed in
|
Gogithub.com/go-gitea/giteapkg:golang/github.com/go-gitea/giteaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until then, consider restricting OAuth2 token exchanges or applying compensating controls to limit exposure.
Description
Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected verifier check.