CVE-2026-103670 json
Gitea trusted workflow cancellation by unapproved fork runs
published last mo. modified 28d ago also BIT-gitea-2026-103670 , EUVD-2026-93911 , GHSA-4j4g-m7mr-hp5j
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami gitea 28.0.0
- gitea gitea 28.0.0
- github.com/go-gitea/gitea#39399 pull request
- github.com/go-gitea/gitea/releases/tag/v28.0.0 release
Is CVE-2026-103670 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-12).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitea | <28.0.0 |
28.0.0 |
Affected products
- Gitea Gitea
Classification
- Weakness
-
- CWE-667 Improper Locking
References
-
github.com
/go-gitea/gitea/pull/39399
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-4j4g-m7mr-hp5j
vendor-advisory, advisory
-
blog.gitea.com
/release-of-28.0.0/
release-notes, article
-
github.com
/go-gitea/gitea/releases/tag/v28.0.0
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-103670
web
Sources
- CVE List CVE-2026-103670
- NVD CVE-2026-103670
- OSV BIT-gitea-2026-103670
- Maintainer advisory GHSA-4j4g-m7mr-hp5j
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.