Gitea profiles disclose limited-visibility owners to public-only tokens
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA.
Summary
Gitea before 28.3.0 checks only that a signed-in viewer can see a limited-visibility owner on profile and feed routes, ignoring a token's public-only restriction (CWE-1220). A user with a public-only token, sent over HTTP Basic authentication, can read the profile and public activity of limited-visibility users and organizations. The disclosure reveals existence and profile metadata but grants no write access.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
The web profile and RSS/Atom feed routes of users and organizations checked only whether a signed-in viewer could see a limited-visibility owner, without considering the `public-only` restriction of the personal access token used to authenticate. Any user holding a public-only token could send it over HTTP Basic authentication to read the profile and activity feed of limited-visibility users and organizations, which are hidden from anonymous visitors and refused on the equivalent API routes. The disclosure covers existence, profile metadata and public activity; it does not grant write access.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Gitea to 28.3.0 or later, which contains the fix.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA Gitea (Gitea) Fixed in 28.3.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Gitea 28.3.0
20 records Highest priority Priority MEDIUM 3 MEDIUM, 17 LOW
Other records, highest priority first
- TI-2026-83610 Gitea OAuth2 auto-linking lets attackers take over accountsPriority MEDIUM 49
- TI-2026-83601 Gitea public-only token can expose private OCI blobs through package mountsPriority MEDIUM 47
- TI-2026-83594 Gitea public-only token bypass exposes private repository jobsPriority MEDIUM 47
Vendor assessments
Timeline
- 2026-11-01 Threatist record created from CVE-2026-119627
- 2026-11-04 Affected versions changed · Red Hat
- 2026-11-04 CVSS score added · Red Hat
- 2026-11-06 CVSS score added · CISA ADP
- 2026-11-06 CISA SSVC decision points changed
References
Patch 4
More Gitea vulnerabilities
- TI-2026-42785 Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. KEVCVSS 3.1CRITICAL 9.8
- TI-2026-42033 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts CVSS 3.1CRITICAL 9.8
- TI-2026-40842 Privilege Escalation via Access Token Scope Escalation in API CVSS 3.1CRITICAL 9.8
- TI-2026-16922 Gitea Docker image trusts spoofable reverse-proxy headers by default CVSS 3.1CRITICAL 9.8
- TI-2026-42043 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting CVSS 3.1CRITICAL 9.1
- TI-2026-40381 OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes CVSS 3.1CRITICAL 9.1
Sources
- CVE-2026-119627 · CVE Program
- CVE-2026-119627 · NVD
- FIRST EPSS
- CVE-2026-119627 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences