CVE-2026-123065
Gitea deletion of arbitrary attachment files through release edit
Description
When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit a crafted identifier that resolves to the stored file of another attachment and delete it, provided they know that attachment's UUID. The attachment record stayed, so downloads of the affected issue, comment or release file failed. Release edits now only delete the files of attachments that belong to the release.
INFO
Published Date :
Nov. 15, 2026, 10:17 p.m.
Last Modified :
Nov. 15, 2026, 10:17 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Validate attachment ownership before deletion.
- Ensure attachment identifier matches release.
- Review release edit authorization logic.
- Implement secure file deletion procedures.
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-123065.
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-123065 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-123065
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-123065 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-123065 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
Nov. 15, 2026
Action Type Old Value New Value Added Description When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit a crafted identifier that resolves to the stored file of another attachment and delete it, provided they know that attachment's UUID. The attachment record stayed, so downloads of the affected issue, comment or release file failed. Release edits now only delete the files of attachments that belong to the release. Added CWE CWE-22 Added CWE CWE-639 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/123xxx/CVE-2026-123065.json">CVE-2026-123065</a> Added Reference https://blog.gitea.com/release-of-28.4.0/ Added Reference https://github.com/go-gitea/gitea/pull/40120 Added Reference https://github.com/go-gitea/gitea/pull/40268 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.4.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-4p89-xcq8-xfhm