Technical impact
The API routes for releases, release assets, milestones, and repository labels failed to reject changes to archived repositories. A user with write access to an archived repository, or a holder of such a user’s write‑scoped token, could replace or delete release assets while keeping their download URLs, delete releases and tags, and create, edit or delete milestones and labels of a repository that is intended to be read‑only. The fix now returns HTTP 423 Locked for archived repositories, preventing these operations until the repository is unarchived. The flaw is categorized as a CWE‑862 Authorization weakness, permitting unauthorized changes to a repository that should be read‑only.
Affected Systems
All Gitea installations running versions prior to 28.3.0 that expose the API routes for releases, release assets, milestones, and labels are affected. The flaw permits any user or token with write permissions to alter the contents and metadata of an archived repository.
Risk and Exploitability
The vulnerability is exploitable remotely through the standard HTTP API and requires the attacker to possess write permissions or a write‑scoped token. The EPSS score of approximately 0.00266 and the vulnerability not being listed in the CISA KEV catalog indicate a very low probability of exploitation, but the potential to tamper with release history, tags, and metadata poses a significant integrity risk for organizations that rely on archives to preserve project state. The CVSS score is 6.5, indicating moderate severity.