Technical impact
A public‑only personal access token that normally is restricted to read‑only access to public resources can be used to create private repositories in organizations, create private organizations, and generate private repositories from templates. Because the target API endpoints failed to enforce the public‑only scope, an attacker with a legitimate public‑only token that also has write permissions can create resources beyond the token owner’s intended limits. This flaw is an instance of improper access control (CWE‑284), allowing a user to bypass the intended restrictive authorization model and gain privilege escalation opportunities.
Affected Systems
The vulnerability affects Gitea, specifically versions up to and including 1.27.3. The fix was backported to the 28.3.0 release. Administrators should verify that the installed Gitea instance is not running a pre‑28.3.0 version.
Risk and Exploitability
The risk is high because the attacker only needs a legitimate public‑only token with write permissions, which is a credential that an organization may legitimately hand out for automated tasks. The attack vector is through the public API endpoints for repository and organization creation, and it can be executed remotely without additional privileges. The EPSS score of < 1% indicates a very low, but non‑zero, likelihood of exploitation, while the CVSS score of 7.5 classifies the vulnerability as high severity. The lack of scope enforcement creates a serious privilege escalation vector. Administrators should treat this as a critical issue.