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: 6.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized disclosure and manipulation of release attachment metadata
Action: Apply Patch
AI Analysis

Impact

A write‑access user on Gitea releases can, by knowing an attachment’s UUID, link that attachment to a release. This action reveals the file name, size, and download count through the release, and gives the user further rights to rename or delete the attachment. The flaw therefore allows an authorized user to gather sensitive attachment information and potentially alter or remove attachments that should not be exposed.

Affected Systems

The vulnerability affects Gitea repositories. Any deployment running a Gitea version before the 28.2.0 release is susceptible until patched.

Risk and Exploitability

The exploit requires the attacker to have write permission to a repository’s releases, a privilege commonly granted to repository maintainers or trusted collaborators. Because the flaw relies on knowledge of an attachment UUID, the attack is limited to internal or credentialed users. The EPSS score is very low (<1%) and the vulnerability is not listed in CISA KEV. The CVSS score of 6.3 indicates moderate severity. Nonetheless, the potential for data leakage and unauthorized modification of attachments elevates the risk to moderate or high in environments where release writers manage sensitive assets.

Generated by OpenCVE AI on October 20, 2026 at 06:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Gitea 28.2.0 or later, which corrects the attachment linking logic.
  • Enforce least‑privilege on release permissions—grant write access only to trusted users who legitimately need it.
  • Review existing release attachments and remove or rename any that should remain private, especially those that could have been linked through this flaw.

Generated by OpenCVE AI on October 20, 2026 at 06:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'}


Mon, 19 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea

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

cve-icon MITRE

Status: PUBLISHED

Assigner: Gitea

Published:

Updated: 2026-10-19T20:20:57.542Z

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

Link: CVE-2026-110494

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

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

Modified: 2026-10-19T21:17:05.947

Link: CVE-2026-110494

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-20T07:00:13Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key