Gitea contribution heatmap private activity disclosure to public-only tokens
Affects Gitea 28.2.0 and earlier, where a public-only access token can reveal when the profile owner worked in private repositories. Fixed in Gitea 28.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 28.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Gitea, the self-hosted Git service, is affected: its user contribution heatmap API could reveal activity counts and timing from a user's private repositories to anyone holding that user's public-only access token. Repository names and contents were not exposed, but the contribution counts and time patterns leaked private activity levels.
Read the original 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.
What to do
Check whether your setup matches what the bug needs.
Gitea version 28.2.0 or earlier is affected Attacker holds a public-only access token of the profile owner The owner must have contribution activity in private repositoriesUpgrade to a fixed version: 28.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gitea.dev
fixed in 28.3.0
Evidence 5
- Advisory
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-114199
What does this mean?
A public-only personal access token for a profile owner can show the owner's contribution counts and 15-minute activity buckets in the heatmap. These show when the owner worked in private repositories, but repository names and contents are not disclosed.Source: github.com, blog.gitea.com
Am I affected, and how do I check?
Gitea 28.2.0 and earlier are affected, and the owner must have contribution activity in private repositories. Administrators can check the installed version on the admin dashboard or with the gitea binary's version command.Source: github.com, blog.gitea.com
What should I do about it?
Upgrade to Gitea 28.3.0 or later, which fixes the heatmap disclosure.Source: github.com, blog.gitea.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data