CVE-2026-114199

Gitea contribution heatmap private activity disclosure to public-only tokens

Published Nov 1, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
`GET /api/v1/users/{username}/heatmap` computed the contribution heatmap with the repository access of the token owner and ignored the public-only restriction of the access token, unlike the activity feed endpoints. A holder of a user's public-only token could read contribution counts and their 15-minute time buckets that stem from that user's activity in private repositories. Repository names and contents were not disclosed. For public-only tokens the heatmap now only counts activity visible to anonymous users.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.3.0 or later, where the heatmap endpoint respects public‑only token restrictions
  • Revoke or rotate any exported public‑only tokens that may have been shared or used in unsecured settings
  • Audit current token scopes and enforce the least‑privilege principle by limiting public‑only tokens to users who truly need them
  • Apply any additional security hardening recommendations from the Gitea release notes or community advisory

Generated by OpenCVE AI on November 6, 2026 at 17:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description `GET /api/v1/users/{username}/heatmap` computed the contribution heatmap with the repository access of the token owner and ignored the public-only restriction of the access token, unlike the activity feed endpoints. A holder of a user's public-only token could read contribution counts and their 15-minute time buckets that stem from that user's activity in private repositories. Repository names and contents were not disclosed. For public-only tokens the heatmap now only counts activity visible to anonymous users.
Title Gitea contribution heatmap private activity disclosure to public-only tokens
Weaknesses CWE-200
CWE-203
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-203

    Observable Discrepancy

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 6, 2026, 3:37 PM
Reserved
Nov 1, 2026, 8:48 AM
Status
Deferred
Published
Nov 1, 2026, 10:18 AM
Modified
Nov 6, 2026, 4:17 PM