VulnerabilityPublished 1 Nov 2026

CVE-2026-114199: Gitea · Information Exposure

Affects GiteaSource CVE Database V5

Compare

Not known to be exploited : upgrade to 28.3.0 when convenient.

Data as of 1 Nov 2026, 10:07 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 28.3.0

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

cwe-203

What to do

Upgrade Gitea and github.com/go-gitea/gitea to 28.3.0.

Affected software

Product	Affected	Fixed in
Giteagitea.dev	Affected <28.3.0	Fixed in 28.3.0
Gogithub.com/go-gitea/gitea`pkg:golang/github.com/go-gitea/gitea`Other threats	Affected <28.3.0	Fixed in 28.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Gitea to version 28.3.0 or later, where the heatmap endpoint enforces public-only token restrictions by showing only activity visible to anonymous users. No other mitigation is required as the issue is fixed in this release.

Description

A vulnerability in Gitea versions prior to 28.3.0 allowed exposure of contribution heatmap data derived from private repository activity to holders of public-only access tokens. While repository names and contents were not disclosed, unauthorized actors could view contribution counts and their 15-minute time buckets from private repositories. This issue has been fixed in version 28.3.0, where public-only tokens now restrict heatmap data to activity visible to anonymous users.

Impact

Unauthorized actors with public-only tokens could infer user activity patterns in private repositories by viewing contribution counts and their 15-minute time buckets. However, no private repository names or contents were disclosed, limiting the sensitivity of the exposed information. This could lead to unintended exposure of user activity metadata.

Summary

The GET /api/v1/users/{username}/heatmap endpoint in Gitea computed contribution heatmaps using the repository access level of the token owner, ignoring the public-only restriction of the access token. Consequently, users holding a public-only token could access contribution counts and time-segmented activity data from private repositories, although no repository names or contents were exposed. This behavior differed from other activity feed endpoints that respected the public-only token restrictions. The vulnerability is tracked as CVE-2026-114199 and fixed in Gitea version 28.3.0 by limiting heatmap data for public-only tokens to only include activity visible to anonymous users.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Nov 2026, 10:07 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats