Gitea’s pull request review notifier does not attach the pull request to the Actions notification, meaning the fork workflow approval gate does not recognize runs originating from a fork. Review comment or approval events therefore cause the workflow code from the fork’s head to be executed on the base repository’s runners. This flaw permits execution of fork‑controlled workflow code across the intended approval boundary, potentially giving a reviewer the ability to run arbitrary workflow steps on the target repository.

The vulnerability affects instances of the Gitea application. Versions released before 1.27.3 are affected; the fix was incorporated into release 1.27.3 and later.

The CVSS score of 8.8 indicates a high‑severity vulnerability. EPSS information is unavailable, so the current exploitation probability cannot be quantified, and the issue is not listed in the CISA KEV catalog. Based on the description, it is inferred that the likely attack scenario involves an attacker forking a repository, opening a pull request, and then submitting a review comment or approval. Upon that event, the untrusted workflow code is executed on the base repository’s runners, allowing the attacker to run arbitrary workflow steps.