CVE-2026-112887

Gitea Actions task token private repository enumeration

Published Nov 1, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, which repository, organization, project and key filters treated as having no owner restriction, and the token carried no API scope to restrict user-scoped routes. A user who can run a workflow could use the job's token with `GET /api/v1/user/repos` to list every repository on the instance, including private repositories of other users and organizations, with their metadata. Repository contents remained protected by per-repository permission checks. System users now own nothing, and `/api/v1/user` routes other than `GET /api/v1/user` accept only individual and bot accounts.

Analysis

AI-generated

Technical impact

The vulnerability allows a user who can run a Gitea Actions workflow to obtain a token that authenticates as a shared system user. Because that token bypasses owner restrictions on repository queries and lacks API scope limits, calling GET /api/v1/user/repos returns metadata for every repository on the instance—including private ones—while the contents of those repositories remain protected by normal permission checks. This results in a confidentiality compromise, exposing repository existence and descriptive information.

Affected Systems

The issue applies to the Gitea platform. No specific version range is provided in the advisory, but the fix is incorporated in release 28.3.0. The vulnerability affects any Gitea deployment that allows users to execute Actions workflows before that version.

Risk and Exploitability

An attacker must first have permissions to trigger a workflow; the exploit then leverages the task token to enumerate private repository metadata. The EPSS score is < 1% and the CVSS score is 4.3, and the vulnerability is not listed in the CISA KEV catalog, indicating a moderate to low likelihood of widespread exploitation, but still posing a risk to exposed repository metadata. Given the severity of the information disclosure and the lack of automatic mitigation, administrators should prioritize applying the available patch.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.3.0 or later to enforce proper token scoping and remove shared system user privileges.
  • If an upgrade cannot be performed immediately, restrict Action workflow execution to trusted administrators and disable public triggers.
  • Review repository visibility settings and enforce that only authorized users can view private repository metadata; consider disabling the GET /api/v1/user/repos endpoint for shared or system users if possible.

Generated by OpenCVE AI on November 6, 2026 at 17:22 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
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, which repository, organization, project and key filters treated as having no owner restriction, and the token carried no API scope to restrict user-scoped routes. A user who can run a workflow could use the job's token with `GET /api/v1/user/repos` to list every repository on the instance, including private repositories of other users and organizations, with their metadata. Repository contents remained protected by per-repository permission checks. System users now own nothing, and `/api/v1/user` routes other than `GET /api/v1/user` accept only individual and bot accounts.
Title Gitea Actions task token private repository enumeration
Weaknesses CWE-200
CWE-862
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-862

    Missing Authorization

Sources

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