Vulnerability · Published Oct 6, 2026 · Assigned by Gitea

CVE-2026-94205Gitea fork workflow approval bypass through maintainer-triggered events

Critical 9.8

In plain English

A critical-severity incorrect authorization in Gitea from Gitea. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 50% of all known vulnerabilities).

Severity (CVSS 3.1)9.8Critical

Exploit odds (30 days)0.6%top 50.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official 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.

Affected products (as reported)

Vendor	Product	Versions
Gitea	Gitea	0 – through 1.27.3

Weakness: CWE-441, CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

GitHub Security Advisory GHSA-xh39-mxw9-34pp vendor-advisory
Fix: go-gitea/gitea pull request #39399 patch
Gitea 28.0.0 release announcement release-notes
go-gitea/gitea v28.0.0 release release-notes