CVE-2026-123065

Gitea deletion of arbitrary attachment files through release edit

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

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. Because the attachment record stayed, downloads of the affected issue, comment or release file failed. The fix ensures that release edits now only delete the files of attachments that belong to the release.

Affected Systems

The vulnerability affects installations of Gitea running any version prior to 28.4.0. Any repository that allows users to edit releases is vulnerable whenever a collaborator with write access to a repository attempts to modify a release.

Risk and Exploitability

The exploit requires the attacker to know an attachment’s UUID and possess write access to the releases of a repository. While the EPSS score is not available and the vulnerability is not listed in CISA KEV, the combination of common repository permissions and the need to know a UUID makes the risk moderate to high for organizations that grant wide collaboration rights. An attacker can cause denial of service by corrupting downloads of releases, issues, or comments, leading to data loss for users. The lack of publicly available EPSS data does not imply low risk; the vulnerability’s impact on download integrity makes it a priority for patching.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.4.0 or later to apply the approved fix that limits attachment deletions to the release’s own attachments.
  • Restrict write permissions on releases to trusted collaborators, or enforce least‑privilege policies, to reduce the set of users able to trigger the flaw.
  • Monitor release edit logs for unexpected attachment deletions and verify that attachment records match actual storage before associating them with releases.
  • Consider disabling the attachment upload functionality if patch deployment cannot be performed immediately.

Generated by OpenCVE AI on November 15, 2026 at 22:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values 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.
Title Gitea deletion of arbitrary attachment files through release edit
Weaknesses CWE-22
CWE-639
References
Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:14 PM
Reserved
Nov 15, 2026, 8:29 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM