CVE-2026-94205
Gitea fork workflow approval bypass through maintainer-triggered events
- State
- Published
- Severity
- 9.8 Critical
- Published
- Oct 6, 2026
- Updated
- Oct 7, 2026
- Reserved
- Oct 4, 2026
Description
Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 9.8 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CISA-ADP |
Weaknesses
Affected Products
| Product | Versions |
|---|---|
GiteaGitea |
|
References
- GitHub Security Advisory GHSA-xh39-mxw9-34ppvendor-advisory
- Fix: go-gitea/gitea pull request #39399patch
- Gitea 28.0.0 release announcementrelease-notes
- go-gitea/gitea v28.0.0 releaserelease-notes
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.