CVE-2026-27775: Gitea Open Source Git Server · Incorrect Authorization
Affects Gitea Open Source Git ServerSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation 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 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GiteaGitea Open Source Git Server | Affected
| Fixed in– |
GitHubgo-gitea/giteapkg:github/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 an official fix is available, restrict maintainer-edit permissions carefully and monitor repository access closely.
Description
Gitea version 1.25.5 has a vulnerability where branch-specific write permissions are cached improperly during a pre-receive hook session. This flaw allows a user with per-branch maintainer-edit rights to reuse that permission across other refs, effectively escalating their access to full repository write privileges. The vulnerability is classified under CWE-863 and carries a high severity score of 8.8.