Bug 2555279 (CVE-2026-110494)

Summary: CVE-2026-110494 code.gitea.io/gitea: Gitea: Unauthorized attachment modification via release attachment linking
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerability-draftAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: gbenhaim, niyer, twaugh
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Gitea. When adding attachments to a release, the application does not verify whether an attachment is already linked to an issue or comment. An authenticated user with write permissions to repository releases who knows the Universally Unique Identifier (UUID) of an existing attachment can link it to a release. This flaw permits unauthorized modification or deletion of the attachment, as well as information disclosure of attachment metadata, including file names, sizes, and download counts.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-18 19:01:26 UTC
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.