Technical impact
A permission check for the web endpoint that deletes attachments was omitted when the request originated from a user who had originally uploaded the attachment. The endpoint was reachable to anyone with read access to issues or pull requests, so a former contributor who lost write rights could still delete a release asset they had uploaded. The vulnerability permits the removal of released artifacts without the appropriate ownership or repository write permissions, potentially impacting the integrity of release history and automated deployment pipelines.
Affected Systems
The flaw exists in Gitea installations where the attachment deletion endpoint omitted a permission check for users who had uploaded the attachment. The vulnerability can affect repositories where users have read access to issues or pull requests, enabling a former contributor to delete release assets they had previously uploaded. The fixed behavior now requires that the deletion request originates from the uploader and that the attachment is not linked to an issue, comment, or release.
Risk and Exploitability
The EPSS score for this vulnerability is not available, and it is not listed in the CISA KEV catalog, indicating no current evidence of public exploitation. The CVSS metric is not specified in the advisory, but the impact is clear: an attacker with read access to issues or pull requests can delete a previously uploaded release asset. The risk to a repository depends on the importance of its released assets; loss of artifacts could disrupt CI/CD workflows compromise build reproducibility. While the vulnerability requires only standard web access, the lack of a public exploit does not reduce its potential impact for affected deployments.