CyberRota Analysis
AI-GeneratedThe vulnerability allows collaborators with write access to the Code unit to delete published releases from a repository, despite lacking write access to Releases, due to insufficient checks in the tag deletion handler. This could lead to permanent loss of important releases and their attachments, impacting project integrity and availability. Organizations using Gitea should prioritize addressing this issue, especially those with collaborative workflows involving multiple contributors.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
The Gitea web route for deleting tags (`POST /{owner}/{repo}/tags/delete`) requires only write access to the Code unit, but shares its handler with release deletion and did not check that the target was a plain tag. A collaborator with Code write access and without Releases write access could permanently delete published releases of that repository, including their attachments. Protected tag rules covering the release tag still blocked the deletion.
Related CVEs
Other vulnerabilities affecting the same vendor(s)