{"vulnerability": "CVE-2026-66877", "sightings": [{"uuid": "b8997d27-b43a-4b10-a4f9-b09f690ab06c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-66877", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117441029671314963", "content": "CVE-2026-66877 Gitea fork workflow approval bypass through concurrency cancellation 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.\nhttps://www.cve.org/CVERecord?id=CVE-2026-66877https://github.com/go-gitea/gitea/security/advisories/GHSA-v2w8-m4gr-qj65https://blog.gitea.com/release-of-1.27.3/https://github.com/go-gitea/gitea/pull/39005https://github.com/go-gitea/gitea/pull/39018https://github.com/go-gitea/gitea/releases/tag/v1.27.3#gitea #Gitea#CVE_2026_66877#bot", "creation_timestamp": "2026-10-14T19:58:19.465174Z"}]}