CVE-2026-66877
Gitea fork workflow approval bypass through concurrency cancellation
Reported by gitea · Published October 14, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| gitea | Alpine | 1.27.3-r0 |
| code.gitea.io/gitea | Gitea | 1.27.2 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Gitea | Gitea | 0 |
| Gitea | Gitea | 0 |
| alpine | gitea | 0 |
Timeline
- Oct 14, 2026 CVE Published
- Oct 15, 2026 EPSS Score (6 in total, the first dated here)
- Oct 15, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-66877
vulnetix vdb fixes CVE-2026-66877Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-66877/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- GitHub Security Advisory GHSA-v2w8-m4gr-qj65 vendor-advisory
- Gitea 1.27.3 release announcement release-notes
- Fix: go-gitea/gitea pull request #39005 patch
- Fix: go-gitea/gitea pull request #39018 patch
- go-gitea/gitea v1.27.3 release release-notes