CVE-2026-27761
published 2026-07-03CVE-2026-27761: Gitea versions up to and including 1.26.2 allow repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository…
PriorityP424medium4.3CVSS 3.1
AVNACLPRLUINSUCLINAN
EPSS
0.37%
29.4th percentile
Gitea versions up to and including 1.26.2 allow repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository commit data to tokens without the required repository scope.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| code.gitea.io | gitea | >= 0 < 1.27.0 | 1.27.0 |
| code.gitea.io | gitea | >= 0 < 1.26.3 | 1.26.3 |
| gitea | gitea_open_source_git_server | <= 1.26.2 | — |
CVSS provenance
nvdv3.14.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
ghsa9.1CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Gitea: Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents
ghsa·2026-07-21·CVSS 9.1
CVE-2026-58444 [CRITICAL] CWE-863 Gitea: Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents
Gitea: Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents
### Summary
A personal access token (PAT) or OAuth2 token that does **not** carry the
`repository` scope or that is **public-only** is correctly rejected (HTTP 403)
by the recently hardened web content routes (archive download, raw/media file
download, and repository RSS/Atom feeds). However, the repository home page route
`GET /{owner}/{repo}` (handler `repo.Home`) serves the **private** repository's
rendered README, root file/directory tree, description, language statistics,
license, and latest-release information to that same token.
This is a token-scope enforcement bypass and private-repository content
disclosure. It is the same source→sink p
GHSA
Gitea: API access token scope enforcement bypass on repository RSS/Atom feed endpoints leaks private repository commit data
ghsa·2026-07-21·CVSS 9.1
CVE-2026-27761 [CRITICAL] CWE-863 Gitea: API access token scope enforcement bypass on repository RSS/Atom feed endpoints leaks private repository commit data
Gitea: API access token scope enforcement bypass on repository RSS/Atom feed endpoints leaks private repository commit data
### Summary
A Gitea personal access token (PAT) restricted to a non-repository scope (e.g. `read:issue`) can read the commit history of any private repository the token owner can access, via the repository RSS/Atom feed endpoints. The same token is correctly denied (403) on `/raw`, `/media`, `/archive`, and the contents API. It leaks commit SHAs, full commit messages (which frequently contain secrets and internal context), and committer name + email.
### Details
Gitea enforces PAT scope on repository-content endpoints via `checkDownloadTokenScope()` (added in PR #37698, extended to the archive endpoint by the CVE-2026-20706 fix in 1.26.2). The RSS/Atom feed handlers
VulDB
Gitea up to 1.26.2 Access Token authorization (GHSA-3pww-vcvm-3gmj)
vuldb·2026-07-04·CVSS 4.3
CVE-2026-27761 [MEDIUM] Gitea up to 1.26.2 Access Token authorization (GHSA-3pww-vcvm-3gmj)
A vulnerability marked as problematic has been reported in Gitea up to 1.26.2. The affected element is an unknown function of the component Access Token Handler. This manipulation causes incorrect authorization.
This vulnerability is handled as CVE-2026-27761. The attack can be initiated remotely. There is not any exploit available.
It is suggested to upgrade the affected component.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-07-03
Published