Vulnerability · CVE-2026-103670
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.
Published Oct 6, 2026 · corrected/updated Oct 15, 2026 · gitea gitea · evidence confidence high
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 enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-103670 is a high public vulnerability record for gitea gitea. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether gitea gitea is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: gitea/gitea. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 7.5 (technical impact); EPSS 0.2% (30-day exploitation probability). It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-667. Sources contributing to this record: cve_org, epss, nvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 6, 2026 · NIST NVD
Detected
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 enabled, without approval and without
Oct 15, 2026 · NIST NVD
Updated
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 enabled, without approval and without
Affected
- cpe gitea/giteaversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-103670
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-103670
30-day exploitation probability 0.2%
first.org - NIST NVDVulnerability recordCVE-2026-103670
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
nvd.nist.gov