CVE-2026-94205
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.36%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 9.8 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.36% probability · 28th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-441, CWE-863
- Affected
- gitea/gitea
- Source
- 88ee5874-cf24-4952-aea0-31affedb7ff2
EPSS moved from 0.1% on 7 October 2026 to 0.4% on 22 October 2026.
References
- https://blog.gitea.com/release-of-28.0.0/Release Notes
- https://github.com/go-gitea/gitea/pull/39399Patch
- https://github.com/go-gitea/gitea/releases/tag/v28.0.0Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34ppExploit, Mitigation, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.