Vulnerability in Gitea

[ Description ]Official 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.

[ Fixes ]Fixes and patches

• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ Advisories ]Government CERT advisories

• BSI CERT-Bund6 Oct 2026WID-SEC-2026-3792

  Gitea: Multiple vulnerabilities Translated from German

  CVE-2026-103670CVE-2026-94205CVE-2026-103059+26 more CVEs

[ References ]References

• blog.gitea.com/release-of-28.0.0Release Notes
• github.com/go-gitea/gitea/pull/39399Patch
• github.com/go-gitea/gitea/releases/tag/v28.0.0Release Notes
• github.com/go-gitea/gitea/security/advisories/GHSA-93pj-3x56-5gc2MitigationVendor Advisory