VulnerabilityPublished 1 Nov 2026

CVE-2026-119627: Gitea · Insufficient Granularity of Access Control

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:21 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.

What to do

Upgrade Gitea and go-gitea/gitea to 28.3.0.

Affected software

Product	Affected	Fixed in
Giteagitea.dev	Affected <28.3.0	Fixed in 28.3.0
GitHubgo-gitea/gitea`pkg:github/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 this access control issue has been fixed. No other mitigation is indicated or required according to the available information.

Description

CVE-2026-119627 is an access control vulnerability in Gitea affecting versions prior to 28.3.0. It allows users with a public-only personal access token to access profile and activity feed information of limited-visibility users and organizations, which should be hidden from anonymous visitors. The vulnerability exposes existence, profile metadata, and public activity but does not allow write access.

Impact

The impact is limited to unauthorized disclosure of existence, profile metadata, and public activity of limited-visibility users and organizations. There is no write access or modification capability granted by this vulnerability. It compromises privacy by exposing information that should be hidden from users authenticated only with public-only tokens and anonymous visitors.

Summary

The vulnerability in Gitea involves insufficient granularity of access control on web profile and RSS/Atom feed routes. The system only checks if a signed-in viewer can see a limited-visibility owner but fails to consider the 'public-only' restriction of the personal access token used for authentication. Consequently, any user with a public-only token can use HTTP Basic authentication to read profiles and activity feeds of limited-visibility users and organizations. This exposure bypasses intended visibility restrictions that apply to anonymous visitors and the equivalent API routes. The issue was fixed in version 28.3.0.

CWE-1220Insufficient Granularity of Access Control (opens in a new tab)
Base weakness
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack the required granularity
Architecture and Design · Implementation · Testing
Access-control-policy protections must be reviewed for design inconsistency and common weaknesses.; Access-control-policy definition and programming flow must be tested in pre-silicon, post-silicon testing.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (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:20 UTC

WeaknessesCWE-1220

Technical details

References

Community reviews

Related threats