Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gitea versions before 1.27.0 are affected. A personal access token or OAuth2 token that lacks the repository scope, or that is public-only, is still accepted by the repository home page route (GET /{owner}/{repo}) and can read a private repository's README, root file listing, description, languages, license and latest release. An attacker needs such a token belonging to a user with access to the private repository. Upgrade to Gitea 1.27.0 or later. The source gives no workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0036, the 30th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:57 UTC First seen by agentprime
- 31 Oct 2026, 14:57 UTC Confirmed by OSV