CVE-2026-129341

Gitea release asset deletion by former writers

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after losing write access to the repository. The endpoint now only deletes attachments that the user uploaded and that are not yet linked to an issue, comment or release.

Analysis

AI-generated

Technical impact

A permission check for the web endpoint that deletes attachments was omitted when the request originated from a user who had originally uploaded the attachment. The endpoint was reachable to anyone with read access to issues or pull requests, so a former contributor who lost write rights could still delete a release asset they had uploaded. The vulnerability permits the removal of released artifacts without the appropriate ownership or repository write permissions, potentially impacting the integrity of release history and automated deployment pipelines.

Affected Systems

The flaw exists in Gitea installations where the attachment deletion endpoint omitted a permission check for users who had uploaded the attachment. The vulnerability can affect repositories where users have read access to issues or pull requests, enabling a former contributor to delete release assets they had previously uploaded. The fixed behavior now requires that the deletion request originates from the uploader and that the attachment is not linked to an issue, comment, or release.

Risk and Exploitability

The EPSS score for this vulnerability is not available, and it is not listed in the CISA KEV catalog, indicating no current evidence of public exploitation. The CVSS metric is not specified in the advisory, but the impact is clear: an attacker with read access to issues or pull requests can delete a previously uploaded release asset. The risk to a repository depends on the importance of its released assets; loss of artifacts could disrupt CI/CD workflows compromise build reproducibility. While the vulnerability requires only standard web access, the lack of a public exploit does not reduce its potential impact for affected deployments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to the latest available version to apply the fixed permission check.
  • Reassess repository permissions to ensure users who should not delete assets have their access restricted to the minimal necessary level, even with read permissions to issues or pull requests.
  • Audit release assets for unexpected deletions and re-upload any that were inadvertently removed by former contributors.

Generated by OpenCVE AI on November 15, 2026 at 22:50 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 The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after losing write access to the repository. The endpoint now only deletes attachments that the user uploaded and that are not yet linked to an issue, comment or release.
Title Gitea release asset deletion by former writers
Weaknesses CWE-863
References
Weaknesses

Sources

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