Technical impact
The vulnerability allows an attacker with only read permission on a Gitea repository that is still in the creation phase—such as during a migration, fork, or template operation—to push branches or tags because Git over HTTP lowered the required permission for pushes from write to read. Since repositories under creation lack server‑side hooks, the usual enforcement of write access is bypassed. This enables insertion of arbitrary code or data into the repository, compromising integrity and potentially delivering malicious content to downstream consumers.
Affected Systems
Gitea installations running a version prior to 28.4.0 are affected, as that is the release that introduced checks to block pushes to repositories that are still being created.
Risk and Exploitability
The flaw is exploitable via the standard HTTP Git protocol and requires only read‑level access that a legitimate user might be granted. Because the attack requires no additional privileges and affects any repository in a transient state, the risk is moderate to high for environments where users can initiate migrations or forks. The EPSS score is not available, and the vulnerability is not yet listed in CISA’s KEV catalog, but the straightforward nature of the attack vector warrants timely remediation.