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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Gitea | Gitea | ≤ 28.0.0 | — |
Advisories 1
- WID-SEC-2026-3792 Gitea: Mehrere Schwachstellen BSI CERT-Bund (WID) · Oct 6, 2026
References
- GitHub Security Advisory GHSA-vvqw-mjq8-x248 vendor-advisory
- Fix: go-gitea/gitea pull request #39501 patch
- Fix backport to release/v28: go-gitea/gitea pull request #39507 patch
- Gitea 28.1.0 release announcement release-notes
- go-gitea/gitea v28.1.0 release release-notes