Technical impact
When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit a crafted identifier that resolves to the stored file of another attachment and delete it, provided they know that attachment’s UUID. Because the attachment record stayed, downloads of the affected issue, comment or release file failed. The fix ensures that release edits now only delete the files of attachments that belong to the release.
Affected Systems
The vulnerability affects installations of Gitea running any version prior to 28.4.0. Any repository that allows users to edit releases is vulnerable whenever a collaborator with write access to a repository attempts to modify a release.
Risk and Exploitability
The exploit requires the attacker to know an attachment’s UUID and possess write access to the releases of a repository. While the EPSS score is not available and the vulnerability is not listed in CISA KEV, the combination of common repository permissions and the need to know a UUID makes the risk moderate to high for organizations that grant wide collaboration rights. An attacker can cause denial of service by corrupting downloads of releases, issues, or comments, leading to data loss for users. The lack of publicly available EPSS data does not imply low risk; the vulnerability’s impact on download integrity makes it a priority for patching.