Quick answers
- Is CVE-2026-114199 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114199 being exploited in the wild.
- How severe is CVE-2026-114199?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-114199?
- 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-114199 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-114199?
- 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 GET /api/v1/users/{username}/heatmap endpoint failed to enforce the public-only token scope restriction when computing contribution heatmaps, computing results using the token owner's repository access instead of the token's declared permissions. This was inconsistent with other activity feed endpoints which correctly applied scope restrictions. An attacker with a public-only token could exploit this to read contribution counts and 15-minute time-bucket data from activity in repositories they cannot otherwise access via that token.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed