Technical impact
The vulnerability allows an authenticated user to reply to a code review comment by providing a review ID that belongs to a different pull request. Because the system accepted the ID, the new comment was attached to that review and included the diff context of the commented lines. As a result, an attacker could expose the content of private code diffs from repositories they are not authorized to view. This reflects an authorization bypass through user‑controlled input (CWE‑639).
Affected Systems
Affected systems include installations of Gitea prior to the 28.4.0 release; the issue existed in all versions that did not enforce review‑ID validation on replies made through the web interface, the API, or by incoming mail.
Risk and Exploitability
The exploit requires only that the user is authenticated to the Gitea instance; no additional privileges are required. Because the flaw can reveal private repository data, the confidentiality risk is high, though the CVSS score is not publicly available. The vulnerability is not listed in the CISA KEV catalog and no EPSS score is available, suggesting limited documented exploitation but that does not diminish the potential impact. A remediation that restricts replies to reviews belonging to the same pull request mitigates the risk.