CVE-2026-116289

Gitea public-only token bypass through Actions runner registration

  • Critical 9.1

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.

Key facts

Published
1 Nov 2026
Last changed
6 Nov 2026
Assigned by
Gitea
EPSS
0.277% likely to be exploited in the next 30 days, higher than 20.332% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.1CVSS 3.1, Criticalfrom CISA (ADP container)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
GiteaGitea
  • Default status: unaffected
  • 0 up to but excluding 28.3.0 (affected)

Timeline

  1. 1 Nov 2026 Published

Weakness

References