← Back to search

CVE-2026-103670

7.5 HIGHpublic exploit available

Published 2026-10-06 · Updated 2026-10-07

AI risk analysis

Summary
A Gitea Actions concurrency cancellation flaw allows attackers to interrupt in-progress trusted runs without approval by creating pull requests from forks, potentially disrupting deployments on self-hosted runners.
Exploitability
Exploitation is moderately easy requiring only fork PR creation with a workflow that shares a concurrency group with cancel-in-progress enabled, no code execution needed.
Blast radius
The impact could be significant for self-hosted runners where interrupted runs might leave partial deployment states or cause service disruptions.
Detection
Monitor for unexpected cancellation events in workflow run logs where fork PRs are involved, particularly when concurrent runs share the same concurrency group with cancel-in-progress enabled.
Prioritized remediation
Upgrade to Gitea 2.590 or later to fix the concurrency cancellation logic.
ci-cdconcurrencygiteaworkflow

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.

NVD 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.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Weaknesses

CWE-667

Public exploit & PoC references

All references

Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.

Related CVEs

Related by shared AI tags and CWE weakness class. Browse the full archive.