---
id: "CVE-2026-110494"
kind: "vulnerability"
aliases: ["CVE-2026-110494"]
title: "Gitea-style forge: release attachment check let writers rename or delete others' files"
severity: "medium"
cvss: 6.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "release-attachments", "self-hosted"]
not_affected_if: ["no-untrusted-write-users"]
published_at: "2026-10-18T19:16:33+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T04:01:48+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110494", "first_seen_at": "2026-10-23T21:57:17+00:00"}]
---

# Gitea-style forge: release attachment check let writers rename or delete others' files

Adding an attachment to a release did not check whether the attachment was already linked to an issue or comment. A user with write access to a repository's releases who knew an attachment's UUID could link it to a release, read its file name, size and download count, and rename or delete it.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110494

## From the sources

Adding attachments to a release checked the repository and release of an attachment but not whether it was already linked to an issue or comment. A user with write access to the releases of a repository, who knew the UUID of an attachment in that repository, could link it to a release. This exposed the file name, size and download count of the attachment through the release and allowed the user to rename or delete it.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_