CVE-2026-128365

Gitea required approval bypass through team review request removal

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
Removing a team's review request looked up a review by the negated team ID, which for the team with ID 2 is the ID of the built-in Actions user, and marked the review it found as official. In the organization that owns that team, a user who can change the review requests of a pull request could make an approval left by the Actions user count toward the approvals required by branch protection. Merging still required permission to merge. Removing a team review request no longer changes any review.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the official Gitea patch by upgrading to version 28.4.0 or later
  • Disable the team review requests feature in repositories that do not require it
  • Restrict the permission to modify pull request review requests to a minimal set of trusted users and regularly review those privileges

Generated by OpenCVE AI on November 15, 2026 at 22:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description Removing a team's review request looked up a review by the negated team ID, which for the team with ID 2 is the ID of the built-in Actions user, and marked the review it found as official. In the organization that owns that team, a user who can change the review requests of a pull request could make an approval left by the Actions user count toward the approvals required by branch protection. Merging still required permission to merge. Removing a team review request no longer changes any review.
Title Gitea required approval bypass through team review request removal
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:14 PM
Reserved
Nov 15, 2026, 8:31 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM