Technical impact
A pull request review created through the API with a draft status (the event field set to PENDING or omitted) was incorrectly added to the pull request timeline and announced in notifications and activity feeds just as if it had been submitted. The review content and any line comments became visible to every viewer of the pull request, including anonymous users on a public repository, before the reviewer actually finished the review. This flaw enables an attacker to obtain sensitive code review content in draft form that was intended to remain private until final submission.
Affected Systems
The vulnerable product is Gitea. While no specific version list is provided, the issue was fixed in the 28.4.0 release, so any Gitea installation running a version older than 28.4.0 that creates pull request reviews via the API may be vulnerable.
Risk and Exploitability
The CVSS score and EPSS are not available, and the vulnerability is not listed in CISA’s KEV catalog, which suggests limited exploitation data. However, the flaw allows a legitimate API user with write permission to a repository to cause unauthenticated or anonymous visibility of draft review content, resulting in a direct information disclosure. The attack vector is through the API, and the exploit requires no special conditions beyond the ability to create a draft review. Post‑patch, pending reviews are no longer added to the timeline until they are submitted, eliminating the disclosure path.