CVE-2026-103670: Gitea Vulnerability in Workflow Cancellation by Unapproved Fork Runs

gitea Updated 16 Oct 2026

Summary

16/10/2026
Yes i
High
Not published

CVE-2026-103670: Gitea trusted workflow cancellation by unapproved fork runs. Affects gitea versions < 28.0.0. Fixed in 28.0.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Gitea is an open-source self-hosted Git service that provides a user-friendly interface for managing Git repositories. It supports collaborative development through features like pull requests, issue tracking, and CI/CD workflows via Gitea Actions. This vulnerability affects Gitea's workflow management, specifically in how it handles concurrent actions from forked repositories.

Vulnerability Detail

The vulnerability arises from the way Gitea Actions manages concurrency groups. When a new run is initiated, older runs in the same group are cancelled without verifying if the new run requires approval. This flaw allows users to cancel trusted in-progress runs from forked pull requests, potentially disrupting deployments and leaving the system in an inconsistent state. The issue is particularly critical for self-hosted runners, where such interruptions can lead to partial deployments and operational issues.

How To Fix

Minimum fixed version

28.0.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, consider disabling the cancel-in-progress feature for workflows that may be affected by this vulnerability. This can be done by modifying the workflow configuration to prevent automatic cancellation of older runs.

Conclusion

CVE-2026-103670 presents a significant risk to Gitea users, particularly those using forked repositories. It is crucial to update to the patched version to mitigate the risk of unauthorized cancellations of workflow runs. Temporary workarounds can help, but a permanent fix is recommended.

See every vulnerability recorded for gitea →

Share this vulnerability

FAQ

CVE-2026-103670 is a security vulnerability in Gitea that allows unapproved fork runs to cancel trusted workflow executions.

Users of Gitea who utilize forked repositories for pull requests and have enabled the cancel-in-progress feature are at risk.

The vulnerability can lead to unintended cancellations of in-progress deployments, causing partial states and operational disruptions.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If an immediate update is not possible, consider disabling the cancel-in-progress feature as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for gitea.

How To Fix

Minimum fixed version

28.0.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback