CVE-2026-66877Gitea fork workflow approval bypass through concurrency cancellation
Updated under an hour ago ()
Does this affect you?
It affects Gitea. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.43%, higher than 36% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 8.1 HIGH (v3.1, CISA ADP)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Weakness (CWE)
- CWE-284
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.43% (percentile 36)
- Assigned by
- Gitea
- NVD analysis
- Deferred
- Record last updated
- Oct 14, 2026
- First seen by InfoSec Signals
- Oct 14, 2026
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.