CVE-2026-104626
Gitea ≤ 28.0.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-104626 is a high-severity Improper Enforcement of Behavioral Workflow (CWE-841) vulnerability in Gitea Gitea. Its CVSS base score is 8.8 (High).
Operationally, ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-93907
Vulnerability Data
A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. When a later run in that group cancels the blocked job, the…
more
run becomes terminal while still marked as needing approval. If a maintainer later approves the run, Gitea passed the already-cancelled job back through concurrency preparation, set it to waiting, and made it claimable by a matching runner, executing fork-controlled workflow code. Exploitation requires the maintainer's later approval action, Actions to be enabled, and a runner that accepts the repository's jobs.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle requires explicit workflow enforcement in multi-step processes.
A.8.26 only requires that workflow-enforcement requirements be identified during requirements gathering; it performs no enforcement itself and leaves the weakness fully exploitable
A.8.27 mandates security-by-design principles (least privilege, default deny, fail securely, distrust external input, defense-in-depth, assume-breach, zero-trust verification) plus design reviews that can catch and block many workflow-sequence enforcement gaps before they ship, but leaves a bounded remainder (e.g. complex multi-step business-process flows whose required ordering is not captured by any listed principle or standard attack-pattern review).
Secure coding practices can prevent missing workflow checks but do not define the control itself.
Security testing can detect workflow bypasses but does not enforce them at runtime.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-841, a class-level weakness, and none of its children carries one either.