CVE-2026-103670

Gitea trusted workflow cancellation by unapproved fork runs

Published Oct 6, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability allows a user who can open a pull request from a fork to cancel trusted in‑progress Gitea Actions runs that share a concurrency group without approval. This cancellation can interrupt self‑hosted deployments and leave partial state behind. The flaw originates from an improper check of the new run’s approval status before canceling older runs, which results in an unauthorized cancellation operation. The primary weakness is an absence of proper access control.

Affected Systems

The affected product is Gitea, version information is not explicitly provided in the CVE. The fix appears in the 28.0.0 release. Users running older Gitea versions are vulnerable if they allow forks to create pull requests and enable the `cancel‑in‑progress` setting on workflows.

Risk and Exploitability

The vulnerability has a CVSS score of 7.5 and an EPSS score of < 1%, indicating moderate to high severity but low likelihood of exploitation. The potential to disrupt critical self-hosted deployments suggests a moderate to high risk of availability impact. Because the attack vector requires only the ability to open a fork-based pull request, an attacker with even limited collaborator access can exploit it. Governance of fork permissions and prompt version upgrades are recommended to mitigate this risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Gitea v28.0.0 or later where the issue is fixed.
  • Disable fork‑based pull request creations or restrict fork permissions to trusted users until an upstream patch is applied.
  • Disable the `cancel‑in-progress` option for workflows that handle critical or production deployments, or separate them into their own concurrency groups.
  • Monitor Gitea Action logs for unexpected cancellation events and review workflow statuses regularly.

Generated by OpenCVE AI on October 7, 2026 at 17:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Weaknesses CWE-667
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Weaknesses CWE-284
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
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 3:58 PM
Reserved
Oct 4, 2026, 9:57 PM
Status
Analyzed
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 15, 2026, 2:23 AM