Technical impact
A flaw in Gitea causes the removal of a team review request to be processed incorrectly. When the system looks up the review using a negated team ID, the ID for team 2 resolves to the built‑in Actions user. The review attributed to that user is then marked official, allowing its approval to contribute to the number of approvals required by branch protection rules. Although the merge still requires explicit merge permission, the approval requirement can be inadvertently satisfied, effectively weakening the protection set on the branch.
Affected Systems
Gitea deployments using a release older than 28.4.0 with team review requests enabled are vulnerable. The fix is included in the 28.4.0 release, so any hosted or self‑hosted instance not updated to that version remains at risk.
Risk and Exploitability
Exploitation requires the attacker to possess the ability to modify review requests on a pull request, a privilege typically granted to repository maintainers or users with write access. Once this capability is available, the attacker can remove the team review request and cause the built‑in Actions user’s approval to be counted officially, thereby bypassing the branch protection approval count. EPSS data is not available and the vulnerability is not listed in CISA KEV, but the lack of a CVSS score does not diminish the fact that the flaw allows critical approval criteria to be satisfied downstream. The risk is therefore moderate to high for environments where privileged users can alter review requests, especially if those users are compromised or misbehaved. Monitoring of review request changes is advisable until the CVE is patched.