Gitea · Gitea · published 2026-10-06
CVE-2026-103670Gitea trusted workflow cancellation by unapproved fork runs
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-103670 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 12% of all CVEs. This Gitea vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Gitea 28.1.0, 28.0.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.1.0, 28.0.0.
Patch events
DevOpsGitea
Gitea security releases: 28.1.0, 28.0.0
Upgrade to
28.1.028.0.0Why: CVE-2026-89182: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (12th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
0through1.27.3(affected)
Description (from the CVE record)#
When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.
Quoted from the CVE Program record.