Answer in brief
CVE-2026-123065 records a Unknown severity vulnerability in Gitea deletion of arbitrary attachment files through release edit. The current sources do not mark it as known exploited. The current feed maps Gitea/Gitea (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Gitea/Gitea (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Gitea/Giteageneric | >=1.15.0 <28.4.0 | 28.4.0 |
Published upstream
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.