The GET /api/v1/user/actions/runners/registration-token endpoint (and its owner- and repository-level equivalents) creates a new runner registration token if none exists, yet the API scope middleware classifies it as read-only because it is a GET request. A holder of a leaked read:user-scoped token can therefore mint a registration token and register a malicious Actions runner that executes workflow jobs with access to repository secrets and source code.
Metrics
Affected Vendors & Products
References
History
Thu, 13 Aug 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The GET /api/v1/user/actions/runners/registration-token endpoint (and its owner- and repository-level equivalents) creates a new runner registration token if none exists, yet the API scope middleware classifies it as read-only because it is a GET request. A holder of a leaked read:user-scoped token can therefore mint a registration token and register a malicious Actions runner that executes workflow jobs with access to repository secrets and source code. | |
| Title | Gitea runner registration-token GET endpoint performs a write under a read-only token scope | |
| Weaknesses | CWE-269 | |
| References |
|
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-08-13T16:48:52.623Z
Reserved: 2026-03-03T03:25:28.686Z
Link: CVE-2026-24059
No data.
Status : Received
Published: 2026-08-13T17:17:21.887
Modified: 2026-08-13T17:17:21.887
Link: CVE-2026-24059
No data.
OpenCVE Enrichment
Updated: 2026-08-13T18:45:04Z