Back to CVE records
Critical 9.8Published Oct 6, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects Gitea. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.36%, higher than 28% of scored CVEs.

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
9.8 CRITICAL (v3.1, CISA ADP)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-441, CWE-863
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
0.36% (percentile 28)
Assigned by
Gitea
NVD analysis
Analyzed
Record last updated
Oct 7, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Gitea Gitea
gitea:gitea (from the name)
through 1.27.3
CNA record
gitea gitea
gitea:gitea
before 28.0.0
NVD

References

  • vendor-advisory, exploit, mitigation
  • patch
  • release-notes
  • release-notes

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.