CVE-2026-94205

Gitea fork workflow approval bypass through maintainer-triggered events

Published Oct 6, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.

Analysis

AI-generated

Technical impact

A flaw in Gitea Actions caused the approval requirement for a forked pull request workflow run to be based on the user who triggered the event rather than the pull request author. When a maintainer performed ordinary triage actions such as adding a label, a run was created without requiring approval, but the workflow definition was still taken from the fork head. If Actions is enabled and a matching runner is registered, the fork-controlled workflow code could execute on the base repository's runners without explicit approval, allowing unauthorized code to run with the runner's permissions.

Affected Systems

The vulnerability affects installations of Gitea, with the precise version range not explicitly enumerated in the advisory. It is likely present in releases prior to the 28.0.0 release, which is referenced as a point of remediation.

Risk and Exploitability

The exploit requires Gitea Actions to be enabled and a runner of the appropriate type to be registered. Because the EPSS score is less than 1% and the issue is not listed in the CISA KEV catalog, the current quantitative risk metrics are limited, although the CVSS score of 9.8 indicates a critical severity. However, the nature of the flaw permits execution of arbitrary forked workflow code on the base repository's runners, representing a high‑severity scenario in the absence of an explicit approval gate.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Gitea to the latest stable release that contains the fix for the fork workflow approval bypass.
  • If an update is not yet possible, disable Gitea Actions for forks or restrict maintainer-triggered events until a patch is deployed.
  • Configure workflow permissions to require explicit approval for forked workflows, ensuring that base repository runners do not execute code without authorization.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

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

ssvc

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

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.
Title Gitea fork workflow approval bypass through maintainer-triggered events
Weaknesses CWE-441
CWE-863
References
Weaknesses
  • CWE-441

    Unintended Proxy or Intermediary ('Confused Deputy')

  • CWE-829

    Inclusion of Functionality from Untrusted Control Sphere

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 8:11 PM
Reserved
Oct 4, 2026, 9:57 PM
Status
Analyzed
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 13, 2026, 4:41 PM
Severity
Important
Public date
Oct 6, 2026, 7:25 PM