CVE-2026-27761: Gitea Open Source Git Server · Incorrect Authorization
Affects Gitea Open Source Git ServerSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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:L/I:N/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
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 API token permissions carefully and avoid using tokens with insufficient scope for accessing repository feeds. Monitor vendor communications for updates on patches or official fixes.
Description
Gitea versions up to and including 1.26.2 have a vulnerability where repository RSS and Atom feed endpoints bypass API access token scope checks. This allows tokens without the required repository scope to access private repository commit data via these feeds. The issue is classified as CWE-863 (Incorrect Authorization).