Medium severity · published Oct 18, 2026
CVE-2026-110494
Gitea release attachment re-linking of issue attachments
6.3
CVSS
0.2%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
Low
Integrity
Low
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 9% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GI
Gitea · Gitea
through 28.1.0 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-110494
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-110494
blog.gitea.com
https://blog.gitea.com/release-of-28.2.0/
github.com
https://github.com/go-gitea/gitea/pull/39839
github.com
https://github.com/go-gitea/gitea/pull/39847
github.com
https://github.com/go-gitea/gitea/releases/tag/v28.2.0
github.com
https://github.com/go-gitea/gitea/security/advisories/GHSA-cwq7-782w-pxcc
More from Gitea
9.8
CVE-2026-60004
Gitea Code Injection Vulnerability
9.8
CVE-2026-59774
Gitea Org-mode file disclosure and code execution
9.8
CVE-2026-73278
Gitea WebAuthn bypass during OAuth and OIDC sign-in
9.8
CVE-2026-94205
Gitea fork workflow approval bypass through maintainer-triggered events
9.8
CVE-2022-42968
Gitea before 1.17.3 does not sanitize and escape refs in the git backend