Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 01 Nov 2026 10:00:00 +0000
| 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 |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-11-01T09:48:35.376Z
Reserved: 2026-11-01T08:50:49.229Z
Link: CVE-2026-116289
No data.
Status : Deferred
Published: 2026-11-01T10:18:34.873
Modified: 2026-11-01T10:18:34.983
Link: CVE-2026-116289
No data.
OpenCVE Enrichment
Updated: 2026-11-01T11:30:06Z
-
CWE-863
Incorrect Authorization