CVE-2026-110494: Gitea release attachment access control bypass

CVE-2026-110494 · Severity: info · Published 2026-10-18

Gitea is a self-hosted Git repository management platform. An attacker with write access to a repository's releases could expose metadata (filename, size, download count) of attachments belonging to issues or comments by linking them to a release without authorization, and subsequently rename or delete those attachments.

Technologies: Gitea. Vendors: Gitea.

Quick answers

Is CVE-2026-110494 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-110494 being exploited in the wild.
How severe is CVE-2026-110494?
Informational severity, published 18 October 2026.
Which products and versions are affected?
Gitea before 28.2.0.
Is there a fix for CVE-2026-110494?
Yes: fixed in Gitea 28.2.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110494 attacked?
It is attacked over the network.
Am I affected by CVE-2026-110494?
Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Gitea 28.2.0

Technical details

The vulnerability is an improper access control issue in Gitea's release attachment handling. When adding attachments to a release, the system checked repository and release permissions but failed to verify whether the attachment was already linked to an issue or comment. An authenticated user with release write privileges could exploit UUID knowledge to access cross-context attachments, exposing their metadata and enabling modification or deletion.

Affected products

  • Gitea Gitea before 28.2.0

Timeline

  • 2026-10-18: disclosed
  • 2026-10-18: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.