CVE-2026-66877

published 14 Oct 2026 · updated 15 Oct 2026

Gitea fork workflow approval bypass through concurrency cancellation

8.1HighCVSS 8.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
GiteaGitea<=1.27.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Gitea, strongest first

10.0CriticalCISA KEVPublic exploit

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-66877 severity on Zeptric[![CVE-2026-66877](https://zeptric.io/badge/cve/CVE-2026-66877.svg)](https://zeptric.io/cve/CVE-2026-66877)