# CVE-2026-70400: Gitea private migration creation with public-only tokens

> Attackers with public-only tokens can create private repositories via the migration API, bypassing intended access restrictions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-x58h-3mx5-q44r

## What is CVE-2026-70400?

CVE-2026-70400 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate only on public resources can create a private repository and migration task under the authorizing account or an organization where that user has the necessary permissions. The ordinary private repository-creation route rejects the same token, but the migration path omits that restriction.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-70400?


## How do I fix CVE-2026-70400?

No fix has been published for CVE-2026-70400 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70400 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70400 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 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-70400 in the wild and no public exploit code.

Affected product: Gitea. 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-70400/ (Markdown: https://insights.sbomify.com/CVE-2026-70400/index.md)
```

## Sources

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

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