CVE-2026-103670
Gitea trusted workflow cancellation by unapproved fork runs
- State
- Published
- Severity
- 7.5 High
- Published
- Oct 6, 2026
- Updated
- Oct 7, 2026
- Reserved
- Oct 4, 2026
Description
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 7.5 High | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | CISA-ADP |
Weaknesses
- CWE-667 Improper Locking
Affected Products
| Product | Versions |
|---|---|
GiteaGitea |
|
References
- GitHub Security Advisory GHSA-4j4g-m7mr-hp5jvendor-advisory
- Fix: go-gitea/gitea pull request #39399patch
- Gitea 28.0.0 release announcementrelease-notes
- go-gitea/gitea v28.0.0 releaserelease-notes
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.