# CVE-2026-60018: Gitea OneDev migration denial of service

> Authenticated users can cause denial of service in Gitea by triggering migrations to malicious servers that send oversized or endless responses.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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-46px-6cqx-c5fv

## What is CVE-2026-60018?

CVE-2026-60018 is a medium-severity denial of service 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 OneDev migration downloader reads the entire remote version response into memory without a size limit and uses a client without a timeout. An authenticated user who can start a repository migration can direct it to an attacker-controlled OneDev-compatible server returning an oversized or never-ending response. This can consume memory and hold migration workers, impairing service availability.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-60018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60018 is a medium-severity denial of service 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-60018 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-60018/ (Markdown: https://insights.sbomify.com/CVE-2026-60018/index.md)
```

## Sources

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

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