CVE-2026-110311: Gitea draft release creation disclosing attachment metadata
Creating a draft release through the API returned an assets list that was built from a release without an ID, which matched every attachment that was not linked to a release. A user who could create a draft release in a repository therefore received the metadata (file name, UUID, upload time, size and download count) of issue and comment attachments of repositories they could not read, and of abandoned uploads.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue?
A user must be able to create a draft release through the API in a repository. That user can receive attachment metadata from repositories they cannot read, as well as from abandoned uploads.
What information could be exposed?
The returned metadata can include attachment file names, UUIDs, upload times, sizes, and download counts. The issue describes metadata disclosure, not disclosure of attachment contents.
How can I determine whether a system may have been affected?
Review API activity for draft release creation and inspect the returned assets lists. An affected response may contain attachments not associated with the draft release, including issue or comment attachments from inaccessible repositories or abandoned uploads.