CVE-2026-105267

Gitea tag delete route deletes releases without release permission

Published Oct 6, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Explained, a Gitea route that deletes tags required only write access to code but was shared with release deletion. Because the handler did not confirm the target was a tag, a collaborator with code write permission could delete published releases and their files, causing permanent loss of release data. The flaw constitutes an integrity violation, allowing an attacker to tamper with repository artifacts.

Affected Systems

Gitea is the affected product. No specific version ranges are provided in the CNA data, so any instance of Gitea using the vulnerable tag‑deletion route may be impacted.

Risk and Exploitability

The vulnerability is exploitable via the web interface by any user with code write rights, without needing release‑level permissions. The CVSS score is 8.1, the EPSS score is <1%, and the vulnerability is not listed in the CISA KEV catalog. Risk assessment is based on the potential for permanent data loss. The attack vector is local to the repository, but any collaborator can trigger it, making it a low‑barrier issue for accounts with write access.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to the latest release (≥v28.1.0) where the bug is fixed.
  • Review and tighten repository permissions, ensuring that only users who should be able to delete releases have the required rights.
  • Enable or confirm protected tag rules for release tags to prevent accidental deletions, and consider disabling the tag‑deletion endpoint if possible.

Generated by OpenCVE AI on October 17, 2026 at 08:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
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.
Title Gitea tag delete route deletes releases without release permission
Weaknesses CWE-732
CWE-863
References
Weaknesses
  • CWE-267

    Privilege Defined With Unsafe Actions

  • CWE-732

    Incorrect Permission Assignment for Critical Resource

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 8:02 PM
Reserved
Oct 4, 2026, 10:02 PM
Status
Analyzed
Published
Oct 6, 2026, 10:17 PM
Modified
Oct 13, 2026, 2:38 PM
Severity
Moderate
Public date
Oct 6, 2026, 9:35 PM