# CVE-2026-110311: Gitea API information disclosure in draft release attachments

Source: https://junglewise.ai/threats/cve-2026-110311-creating-a-draft-release-through-the-api-returned-an-assets-list  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-18. Updated: 2026-10-18  
License: CC BY 4.0 with a link back

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

Gitea is a self-hosted Git service with an API for managing repositories and releases. The API incorrectly returned a list of all file attachments from the entire Gitea instance when creating a draft release, exposing metadata (filenames, upload times, sizes) of attachments from private repositories and comments that the user had no permission to access.

Technologies: [Gitea](https://junglewise.ai/threats/technologies/gitea). Vendors: [Gitea](https://junglewise.ai/threats/vendors/gitea).

## Quick answers

**Is CVE-2026-110311 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-110311 being exploited in the wild.

**How severe is CVE-2026-110311?** Informational severity, published 18 October 2026.

**Which products and versions are affected?** Gitea prior to 28.2.0.

**Is there a fix for CVE-2026-110311?** 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-110311 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-110311?** 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

When creating a draft release via the API, the attachments list was built from a release with no ID, causing it to match every attachment not linked to a release instead of only those being added. This allowed an authenticated user with draft-release-creation permission to enumerate metadata of issue and comment attachments across repositories they cannot read, as well as abandoned uploads. The vulnerability requires user authentication and release creation capability.

## Affected products

- Gitea Gitea prior to 28.2.0

## Timeline

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

## References

- [https://blog.gitea.com/release-of-28.2.0/](https://blog.gitea.com/release-of-28.2.0/)
- [https://github.com/go-gitea/gitea/pull/39743](https://github.com/go-gitea/gitea/pull/39743)

## Related threats

- [Gitea account takeover via OAuth2 auto-linking](https://junglewise.ai/threats/cve-2026-120263-when-oauth2-client-account-linking-is-set-to-auto-not-the)
- [Gitea limited-visibility profile disclosure via public-only token](https://junglewise.ai/threats/cve-2026-119627-the-web-profile-and-rss-atom-feed-routes-of-users-and)
- [Gitea token scope bypass in web routes](https://junglewise.ai/threats/cve-2026-119625-the-username-web-route-accepted-personal-access-tokens-over-http)
- [Gitea project boards information disclosure of private pull requests](https://junglewise.ai/threats/cve-2026-119533-repository-and-organization-project-boards-listed-the-pull)
- [Gitea API token scope bypass in repository deletion](https://junglewise.ai/threats/cve-2026-119441-delete-api-v1-orgs-org-repos-deletes-all-repositories-of-an)