Description
Adding attachments to a release checked the repository and release of an attachment but not whether it was already linked to an issue or comment. A user with write access to the releases of a repository, who knew the UUID of an attachment in that repository, could link it to a release. This exposed the file name, size and download count of the attachment through the release and allowed the user to rename or delete it.
Published: 2026-10-18
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 18 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
Description Adding attachments to a release checked the repository and release of an attachment but not whether it was already linked to an issue or comment. A user with write access to the releases of a repository, who knew the UUID of an attachment in that repository, could link it to a release. This exposed the file name, size and download count of the attachment through the release and allowed the user to rename or delete it.
Title Gitea release attachment re-linking of issue attachments
Weaknesses CWE-639
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Gitea

Published:

Updated: 2026-10-18T18:57:26.290Z

Reserved: 2026-10-14T20:08:45.845Z

Link: CVE-2026-110494

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T19:16:33.403

Modified: 2026-10-18T19:16:33.403

Link: CVE-2026-110494

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-18T21:00:10Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key