CVE-2026-24059 Gitea runner registration-token GET endpoint performs a write under a read-only token scope
Attackers with read-only tokens can mint registration tokens to deploy malicious runners, gaining access to repository secrets and code.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-24059?
CVE-2026-24059 is a medium-severity missing authorization vulnerability in Gitea Open Source Git Server, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-269
Which versions are affected by CVE-2026-24059?
How do I fix CVE-2026-24059?
No fix has been published for CVE-2026-24059 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-24059 being exploited?
There is no known exploitation of CVE-2026-24059 in the wild and no public exploit code.
Sources
Also known as GHSA-m7qq-f4rg-v5m5, GHSA-v43r-86x9-8523.