Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the 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-pvjf-7jrm-6w9g 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 8.8 · giteaNVD modified 2026-10-13 17:20
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-pvjf-7jrm-6w9g Mitigation, Vendor Advisory