Technical impact
Gitea allows a user who has forked a repository to edit files via the web editor. During this process the system copies a branch from the base repository into the fork, but it does not verify that the editor has read access to the base repository. As a result, an individual who once had read access but has since lost it—such as when a repository is made private or a collaborator is removed—can continue to duplicate and read any current branches of the original repository. This flaw effectively bypasses normal access control, exposing potentially sensitive source code and violating confidentiality. The weakness involves improper access control (CWE‑284) and missing authorization checks (CWE‑863).
Affected Systems
The affected system is the Gitea platform, version unspecified but the vulnerability is fixed in the 28.4.0 release. Users running earlier Gitea versions that use the web editor for forked repositories are vulnerable.
Risk and Exploitability
The attack does not require advanced preparation beyond having a fork; the user merely initiates a file edit through the web interface. Because the vulnerability removes the necessity to authenticate against the base repository, any party with a fork can exploit it to read private code. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, but the impact is significant for confidentiality. The CVSS score is not provided; however, the combination of unrestricted code disclosure and the lack of a protection mechanism suggests a high severity. Managers should treat this as a critical risk for any organizations relying on Gitea to host or fork private code bases.