CVE-2026-105267

Analyzed Analyzed - Analysis Complete

BaseFortify

Publication date: 2026-10-06

Last updated on: 2026-10-13

Assigner: Gitea Limited

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-06

Last Modified

2026-10-13

Generated

2026-10-19

AI Q&A

2026-10-07

EPSS Evaluated

2026-10-18

NVD

CVE-2026-105267

Affected Vendors & Products

Vendor	Product	Version / Range
gitea	gitea	to 28.1.0 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-732	The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

Executive Summary

This vulnerability in Gitea allows a collaborator with write access to the Code unit to delete published releases, including their attachments, even if they lack Releases write access. The issue occurs because the tag deletion route shares a handler with release deletion but fails to verify if the target is a plain tag, enabling unauthorized release deletion.

Detection Guidance

Check Gitea version with: curl -s http://localhost:3000/api/v1/version | grep version. If version <= 28.0.0, the system is vulnerable. Review logs for POST requests to /{owner}/{repo}/tags/delete with Code:Write access but no Releases:Write access.

Impact Analysis

If you are a repository owner or maintainer, an attacker with write access to your repository's Code unit could delete published releases and their attachments, causing data loss and disrupting software distribution. This could lead to downtime, broken dependencies, or loss of critical release artifacts.

Compliance Impact

This vulnerability could impact compliance by allowing unauthorized deletion of release data, potentially violating data integrity and retention requirements under GDPR or HIPAA. Loss of release artifacts may also hinder audit trails or evidence of compliance.

Mitigation Strategies

Update Gitea to the latest version to ensure the vulnerability is patched. Review repository permissions to ensure collaborators have only the necessary access rights. Specifically, restrict Code write access to prevent unauthorized tag deletions.

Hi! I’m here to help you understand CVE-2026-105267. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70