# 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.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-m7qq-f4rg-v5m5, GHSA-v43r-86x9-8523

## 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 (Improper Privilege Management)

## 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.

## Is CVE-2026-24059 being exploited?

There is no known exploitation of CVE-2026-24059 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24059 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-24059 in the wild and no public exploit code.

Affected product: Gitea Open Source Git Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24059/ (Markdown: https://insights.sbomify.com/CVE-2026-24059/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24059
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24059
- OSV: https://osv.dev/vulnerability/CVE-2026-24059

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24059/
Summaries are generated and may contain mistakes; the official description above is the record.