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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-gitea/gitea/pull/39399 Patch
- https://github.com/go-gitea/gitea/security/advisories/GHSA-4j4g-m7mr-hp5j Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.5 · giteaNVD modified 2026-10-15 02:23
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*