CVE-2026-104632
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
4Patches
Vulnerability mechanics
References
4- github.com/go-gitea/gitea/pull/39399nvdPatch
- github.com/go-gitea/gitea/security/advisories/GHSA-pvjf-7jrm-6w9gnvdMitigationVendor Advisory
- blog.gitea.com/release-of-28.0.0/nvdRelease Notes
- github.com/go-gitea/gitea/releases/tag/v28.0.0nvdRelease Notes
News mentions
3- ⚡ Weekly Recap: 98 Zero-Days, Rogue AI Agents, $100M Crypto Theft, 700 Supermarkets Hit and MoreThe Hacker News · Oct 19, 2026
- Gitea Patches 27 Security Flaws, Including Critical SSH Authentication Bypass and SSRFCyber Security News · Oct 8, 2026
- Gitea: 25 Vulnerabilities Disclosed Together, Including Critical Authentication FlawsVypr Intelligence · Oct 6, 2026