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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-gitea/gitea/pull/39399 Patch
- https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp Exploit, Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.8 · giteaNVD modified 2026-10-13 16:41
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
References 4
- https://blog.gitea.com/release-of-28.0.0/ Release Notes
- https://github.com/go-gitea/gitea/pull/39399 Patch
- https://github.com/go-gitea/gitea/releases/tag/v28.0.0 Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp Exploit, Mitigation, Vendor Advisory