Technical impact
A request to the heatmap API endpoint performed computations using the accessing token’s permissions, ignoring the public‑only restriction applied to the token. This allowed a holder of a public‑only token to retrieve contribution counts and 15‑minute time buckets that reflected the target’s activity in private repositories, while not revealing repository names or contents. The exposed data can give an attacker a detailed activity pattern and timing of a user’s private work, which is a privacy breach and potentially useful for targeted attacks.
Affected Systems
All installations of Gitea before the 28.3.0 release are affected. The vulnerability is present in any deployment where the heatmap endpoint uses the token’s full access level without filtering for public visibility, regardless of the token’s declared scope.
Risk and Exploitability
Trivial for anyone with a public‑only token, the attacker can retrieve private activity metadata via the heatmap endpoint. The CVSS score of 5.3 indicates moderate severity, while the EPSS score is under 1% and the vulnerability is not listed in CISA’s KEV catalog. No special prerequisites beyond possession of the token are needed; there is no additional authentication. The flaw is limited to exposing timing patterns of private work and does not reveal repository contents.