Quick answers
- Is CVE-2026-117646 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117646 being exploited in the wild.
- How severe is CVE-2026-117646?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-117646?
- Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117646 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-117646?
- 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.3.0
Technical details
The repositories, stars, and watching tabs of user profiles and organization repository lists failed to enforce public-only token scope restrictions, allowing disclosure of private repository names and metadata. The vulnerability existed in the web interface for profile pages; the API and activity feeds were already properly restricted. An authenticated request with a public-only scoped personal access token could enumerate private repositories visible to the token owner through these tabs.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed