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