CVE-2026-117646

Gitea private repository listing to public-only tokens on profiles

Published Nov 1, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in request without checking whether the request used a personal access token restricted to public resources (`public-only`). A holder of such a token could list the private repositories visible to the token's owner, and that user's stars and watches of private repositories. The API and the profile activity tab already applied the restriction. The impact is disclosure of repository names and metadata, not of repository content.

Analysis

AI-generated

Technical impact

The vulnerability lies in the way Gitea presents repository, stars, and watching tabs on user profiles and organization home pages. When a signed‑in request uses a personal access token that is designated as "public-only", the application mistakenly includes private repositories in the listings. As a result, an attacker possessing such a token can discover the names and basic metadata of private repositories, as well as the stars and watches of those repositories, without gaining access to the actual contents. The flaw does not allow modification or execution of repository data; it merely exposes metadata that could facilitate further attacks such as social engineering or targeted credential guessing.

Affected Systems

The affected product is Gitea, version information is not explicitly supplied, but the issue appears to have been addressed in the 28.3.0 release and earlier versions that lack the fix.

Risk and Exploitability

The EPSS score is less than 1% and the vulnerability is not listed in the CISA KEV catalog. The CVSS score of 4.3 indicates a moderate severity. The attack vector is authenticated, relying on possession of a public‑only token. An attacker with such a token can retrieve private repository information, representing a medium‑to‑high confidentiality impact when the user owns sensitive projects. Because the exploit does not require elevated privileges beyond a valid token, the risk persists until an update is applied or tokens are revoked.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Gitea to the latest release (28.3.0 or later) where the listing logic has been corrected.
  • Revoke all existing public‑only personal access tokens and regenerate tokens with the correct scope settings, ensuring that only authorized views are granted.
  • Review and, if necessary, adjust Gitea configuration to enforce strict access control on repository listings and token scopes.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Metrics cvssV3_1

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

Type Values Removed Values Added
Weaknesses CWE-200
CWE-284
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in request without checking whether the request used a personal access token restricted to public resources (`public-only`). A holder of such a token could list the private repositories visible to the token's owner, and that user's stars and watches of private repositories. The API and the profile activity tab already applied the restriction. The impact is disclosure of repository names and metadata, not of repository content.
Title Gitea private repository listing to public-only tokens on profiles
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-284

    Improper Access Control

Sources

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