Gitea fork workflow approval bypass through maintainer-triggered events

Summary

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 versions

• gitea.dev

  through 1.27.3

• giteaBitnami

  fixed in 28.0.0

References 4