CVE-2026-110311
Gitea draft release creation disclosing attachment metadata
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.
INFO
Published Date :
Oct. 18, 2026, 7:16 p.m.
Last Modified :
Oct. 18, 2026, 7:16 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Ensure releases have unique IDs.
- Filter attachments by release ID.
- Prevent matching unlinked attachments.
- Limit asset data exposure.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-110311.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-110311 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-110311
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-110311 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-110311 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 88ee5874-cf24-4952-aea0-31affedb7ff2
Oct. 18, 2026
Action Type Old Value New Value 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. Added CWE CWE-200 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/110xxx/CVE-2026-110311.json">CVE-2026-110311</a> Added Reference https://blog.gitea.com/release-of-28.2.0/ Added Reference https://github.com/go-gitea/gitea/pull/39743 Added Reference https://github.com/go-gitea/gitea/pull/39752 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.2.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-8j56-f865-gqq2