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.
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-93pj-3x56-5gc2 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:24
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-93pj-3x56-5gc2 Mitigation, Vendor Advisory