CVE-2026-116289

Gitea public-only token bypass through Actions runner registration

Published Nov 1, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Gitea did not reject personal access tokens restricted to public resources (`public-only`) on the organization Actions runner registration-token endpoint, and the runner registered with the resulting token was not limited to public repositories. Holding only such a token with `write:organization` that belongs to an owner of a public organization, an attacker could register an organization-level runner and receive jobs of the organization's private repositories that have Actions enabled, including the workflow content, Actions secrets and variables, and a task token with access to the private repository. The issue widens what the restricted token can reach; it gives nothing beyond what the owner's full account can already do.

Analysis

AI-generated

Technical impact

Gitea failed to reject personal access tokens designated as public‑only when these tokens were used to register an organization‑level Actions runner. The registration endpoint allowed the token to create a runner that then became capable of executing workflow jobs in all repositories of the organization, including private ones. An attacker who holds such a token with a write:organization scope, even though the token is limited to public resources, can therefore gain access to private repository contents, Actions workflow files, secrets, and variables, effectively escalating privileges within the organization.

Affected Systems

The vulnerability affects the open‑source Gitea platform. No specific version range is listed in the available data, so all installations of Gitea that use the Actions runner registration endpoint are potentially impacted until a fix is applied.

Risk and Exploitability

The vulnerability falls under CWE-266 and CWE-863, involving improper authorization. The CVSS score is 9.1 and the EPSS score indicates an exploitation probability of less than 1 %. Although it is not listed in the CISA KEV catalog, an attacker who holds a public‑only personal access token with write:organization scope could register an organization‑level Actions runner. The registered runner would then receive jobs from the organization's private repositories, exposing workflow files, secrets, variables, and a task token with repository access. This effectively escalates privileges beyond what the token owner can normally obtain, making the risk high for organizations with private repositories and exposed Actions workflows.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.3.0 or later, which contains the fix for the public‑only token validation on runner registration.
  • If an upgrade is not immediately possible, revoke or delete any public‑only personal access tokens that have a write:organization scope for the affected organization.
  • Re‑evaluate token scopes and consider removing the write:organization permission from public‑only tokens or requiring the token to be scoped explicitly to public resources only.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

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

cvssV3_1

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

Type Values Removed Values Added
Weaknesses CWE-266
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description Gitea did not reject personal access tokens restricted to public resources (`public-only`) on the organization Actions runner registration-token endpoint, and the runner registered with the resulting token was not limited to public repositories. Holding only such a token with `write:organization` that belongs to an owner of a public organization, an attacker could register an organization-level runner and receive jobs of the organization's private repositories that have Actions enabled, including the workflow content, Actions secrets and variables, and a task token with access to the private repository. The issue widens what the restricted token can reach; it gives nothing beyond what the owner's full account can already do.
Title Gitea public-only token bypass through Actions runner registration
Weaknesses CWE-863
References
Weaknesses
  • CWE-266

    Incorrect Privilege Assignment

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 6, 2026, 3:34 PM
Reserved
Nov 1, 2026, 8:50 AM
Status
Deferred
Published
Nov 1, 2026, 10:18 AM
Modified
Nov 6, 2026, 4:17 PM
Severity
Moderate
Public date
Nov 1, 2026, 9:48 AM