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.
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Sun, 18 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
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.
Title Gitea release attachment re-linking of issue attachments
Weaknesses CWE-639
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Gitea

Published:

Updated: 2026-10-18T18:57:26.290Z

Reserved: 2026-10-14T20:08:45.845Z

Link: CVE-2026-110494

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T19:16:33.403

Modified: 2026-10-18T19:16:33.403

Link: CVE-2026-110494

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses