Bug 2547035 (CVE-2026-104632) - CVE-2026-104632 code.gitea.io/gitea: Gitea: Arbitrary code execution via workflow approval bypass
Summary: CVE-2026-104632 code.gitea.io/gitea: Gitea: Arbitrary code execution via work...
Keywords:
Status: NEW
Alias: CVE-2026-104632
Product: Security Response
Classification: Other
Component: vulnerability-draft
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-06 19:34 UTC by OSIDB Bzimport
Modified: 2026-11-02 13:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-06 19:34:02 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.