Vulnerability in Gitea

[ Why it matters ]Priority signals

• Critical severity: CVSS 9.8

[ Description ]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.

[ Fixes ]Fixes and patches

• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ Advisories ]Government CERT advisories

• BSI CERT-Bund6 Oct 2026WID-SEC-2026-3792

  Gitea: Multiple vulnerabilities Translated from German

  CVE-2026-103670CVE-2026-94205CVE-2026-103059+26 more CVEs

[ References ]References

• blog.gitea.com/release-of-28.0.0Release Notes
• github.com/go-gitea/gitea/pull/39399Patch
• github.com/go-gitea/gitea/releases/tag/v28.0.0Release Notes
• github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34ppExploitMitigationVendor Advisory