PatchTheCVECVE-2026-103670: When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled
CVE-2026-103670 is a high-severity flaw (CVSS 7.5) affecting gitea. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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-hos
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 88%) |
| CISA exploited list | No |
| Weakness | CWE-667 |
| Published | 2026-10-06 |
| Last modified | 2026-10-15 |
Last updated 2026-10-15 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-103670?
gitea: upgrade to 28.0.0. Exact commands for each OS are on this page.
Is CVE-2026-103670 being exploited?
CVE-2026-103670 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-103670 affect?
CVE-2026-103670 affects gitea. Severity is high (CVSS 7.5). 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,
How urgent is CVE-2026-103670?
Priority 34/100. High severity; Remotely exploitable, no login, no user action
Software pages
Related CVEs
- CVE-2026-101027 HIGH 7.7 UPGRADE When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without ch
- CVE-2026-101029 MEDIUM 4.3 UPGRADE Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns mult
- CVE-2026-103059 CRITICAL 9.1 UPGRADE When Gitea's built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked u
- CVE-2026-103667 MEDIUM 5.4 UPGRADE Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in p
- CVE-2026-86684 HIGH 7.1 UPGRADE The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local