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.
Metrics
Affected Vendors & Products
No data.
No data.
No data.
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sun, 18 Oct 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Gitea draft release creation disclosing attachment metadata | |
| Weaknesses | CWE-200 | |
| References |
|
Projects
Sign in to view the affected projects.
MITRE
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-10-18T18:57:14.140Z
Reserved: 2026-10-14T20:08:45.838Z
Link: CVE-2026-110311
Vulnrichment
No data.
NVD
Status : Received
Published: 2026-10-18T19:16:33.197
Modified: 2026-10-18T19:16:33.197
Link: CVE-2026-110311
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses