Vulnerability in Gitea

[ Description ]Official 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.

[ Fixes ]Fixes and patches

• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD
• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ Advisories ]Government CERT advisories

• BSI CERT-Bund6 Oct 2026WID-SEC-2026-3792

  Gitea: Multiple vulnerabilities Translated from German

  CVE-2026-103670CVE-2026-94205CVE-2026-103059+26 more CVEs

[ References ]References

• blog.gitea.com/release-of-28.1.0Release Notes
• github.com/go-gitea/gitea/pull/39501Patch
• github.com/go-gitea/gitea/pull/39507Patch
• github.com/go-gitea/gitea/releases/tag/v28.1.0Release Notes
• github.com/go-gitea/gitea/security/advisories/GHSA-vvqw-mjq8-x248Vendor Advisory