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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/go-gitea/gitea/pull/39501 Patch
- https://github.com/go-gitea/gitea/pull/39507 Patch
- https://github.com/go-gitea/gitea/security/advisories/GHSA-vvqw-mjq8-x248 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.1 · giteaNVD modified 2026-10-13 14:38
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
References 5
- https://blog.gitea.com/release-of-28.1.0/ Release Notes
- https://github.com/go-gitea/gitea/pull/39501 Patch
- https://github.com/go-gitea/gitea/pull/39507 Patch
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0 Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-vvqw-mjq8-x248 Vendor Advisory