Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 07 Oct 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-667 | |
| Metrics |
cvssV3_1
|
Tue, 06 Oct 2026 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
Tue, 06 Oct 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-284 |
Tue, 06 Oct 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Gitea trusted workflow cancellation by unapproved fork runs | |
| References |
|
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-10-07T15:58:09.298Z
Reserved: 2026-10-04T21:57:35.576Z
Link: CVE-2026-103670
No data.
Status : Awaiting Analysis
Published: 2026-10-06T20:17:14.717
Modified: 2026-10-07T16:17:33.250
Link: CVE-2026-103670
No data.
OpenCVE Enrichment
Updated: 2026-10-07T17:30:17Z