Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gitea versions before 1.27.0 let a token limited to public repositories (public-only, write:repository) update a private pull request head branch through a route on a public base repository. An attacker needs a valid token from a user with normal write access to the private head branch, plus a public base repository and a pull request linking it to the private head. The result is that public base commits can be pushed into the private branch, and push workflows may run when Actions is enabled. Upgrade to Gitea 1.27.0 or later.
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 |
|---|---|---|---|---|
| 9.6 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0058, the 48th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:55 UTC First seen by agentprime
- 31 Oct 2026, 14:55 UTC Confirmed by OSV