Technical impact
The flaw hides in several API and web endpoints that handle both issues and pull requests without verifying which type the resource belongs to. A user who can read only a repository’s issues can therefore access pull‑request information (timeline, attachments, labels, subscriptions, tracked times, reactions) through the issue sub‑resources, and can list pull requests via the repository’s issue‑search and milestone pages; the same privilege inversion applies from pull‑requests to issues. This permissive access turns an issue‑only reader into an unintended pull‑request reader, exposing code review details, attachments, and other potentially sensitive data. The vulnerability is a classic example of an authorization bypass that leads to confidential information leakage, described by CWE-862.
Affected Systems
The issue affects installations of Gitea before the security fixes released in API patches 28.2.0 and 28.3.0 and the UI search/milestone patch in 28.4.0. All affected Gitea instances that have not applied these updates, regardless of other configuration, are at risk, especially repositories where users have read access to issues but not to pull requests. The vendor affected is the Gitea project, and the fix is delivered in the 28.2.0+ releases.
Risk and Exploitability
Because the flaw is exercised through ordinary API calls and web page requests, an authenticated attacker with read‑issue permissions can simply issue a request to the vulnerable endpoints or navigate the web UI to trigger the disclosure. The legitimate use of the API for issue queries is a likely attack vector; there is no known exploitation documented, and the EPSS score is not available. Even without a public exploit, the vulnerability allows an attacker to gain controlled knowledge of pull‑request content, developer identities, and review history. The vulnerability does not require privileges beyond those granted to normal issue readers, thereby widening the attack surface. Consequently, the risk is elevated for any environment that allows issue visibility without equivalent pull‑request restrictions.