CVE-2026-66877GHSA-v2w8-m4gr-qj65
Gitea fork workflow approval bypass through concurrency cancellation
Gitea Gitea
CVSS
8.1HighExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.43%Chance of exploitation activity in the next 30 days, higher than 35% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run's approval requirement. A separate run sharing a job-level concurrency group can cancel a pending job and cause its blocked sibling jobs to be re-emitted and dispatched without approval. This allows unreviewed workflow code to execute on self-hosted runners; fork secrets remain withheld and the run token remains read-only.
Text from CVE List
Affected versions 1
- Giteaaffected: all versions through 1.27.2CVE List
References 5
- github.com/go-gitea/gitea/pull/39005Fixvia CVE List
- github.com/go-gitea/gitea/pull/39018Fixvia CVE List
- github.com/go-gitea/gitea/releases/tag/v1.27.3Fixvia CVE List
- github.com/go-gitea/gitea/security/advisories/GHSA-v2w8-m4gr-qj65Advisoryvia CVE List
- blog.gitea.com/release-of-1.27.3/Referencevia CVE List