Gitea · Gitea · published 2026-10-06
CVE-2026-105267Gitea tag delete route deletes releases without release permission
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-105267 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 32% of all CVEs. This Gitea vulnerability: CVSS 8.1 (v3.1). Fixed upstream in Gitea 28.1.0, 28.0.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.1.0, 28.0.0.
Patch events
DevOpsGitea
Gitea security releases: 28.1.0, 28.0.0
Upgrade to
28.1.028.0.0Why: CVE-2026-89182: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (33th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.1 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
0through28.0.0(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.