Gitea fork workflow job revival through later approval
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. When a later run in that group cancels the blocked job, the run becomes terminal while still marked as needing approval. If a maintainer later approves the run, Gitea passed the already-cancelled job back through concurrency preparation, set it to waiting, and made it claimable by a matching runner, executing fork-controlled workflow code. Exploitation requires the maintainer's later approval action, Actions to be enabled, and a runner that accepts the repository's jobs.
Text from CVE List
Affected versions 1
- Giteaaffected: all versions through 1.27.3CVE List