CVE-2026-94205 Gitea fork workflow approval bypass through maintainer-triggered events
CriticalCVSS 9.8
EPSS 0.62%
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: total
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| Gitea | < 28.0.0; <= 1.27.3 | 28.0.0 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Gitea | <= 1.27.3 | No fix listed |
| Gitea | < 28.0.0 | 28.0.0 |
References
- Red Hat CVE page mitigation vendor-advisory
- Red Hat Bugzilla 2547085 issue-tracking
- www.cve.org
- nvd.nist.gov
- Gitea 28.0.0 release announcement release-notes
- Fix: go-gitea/gitea pull request #39399 patch
- go-gitea/gitea v28.0.0 release release-notes
- GitHub Security Advisory GHSA-xh39-mxw9-34pp exploit mitigation vendor-advisory
- ENISA EUVD EUVD-2026-93919 third-party-advisory