# CVE-2026-70357: Gitea repository migration SSRF through DNS rebinding

> Attackers can bypass network restrictions during repository migration via DNS rebinding to access internal services.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** BIT-gitea-2026-70357, GHSA-p3pc-g8m5-hrrr, MINI-38qh-v4c4-j849, MINI-9w98-x447-fr5h

## What is CVE-2026-70357?

CVE-2026-70357 is a high-severity server-side request forgery vulnerability in Gitea Gitea, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the address between validation and connection to reach a blocked internal address. The affected path is the Git clone operation; validation in the migration HTTP client's dialer does not protect the independently connecting Git subprocess.

Weakness: CWE-918 (Server-Side Request Forgery)

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

1 open source package ship an affected version, including gitea. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitea` | Bitnami | All versions | 28.0.0 |

Products: Gitea Gitea.

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

Upgrade gitea to 28.0.0 or later.

## Is CVE-2026-70357 being exploited?

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

## Other vulnerabilities in Gitea Gitea

- [CVE-2026-60004](https://insights.sbomify.com/CVE-2026-60004/): Gitea Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-73278](https://insights.sbomify.com/CVE-2026-73278/): Gitea WebAuthn bypass during OAuth and OIDC sign-in (critical 9.8)
- [CVE-2026-94205](https://insights.sbomify.com/CVE-2026-94205/): Gitea fork workflow approval bypass through maintainer-triggered events (critical 9.8)
- [CVE-2022-42968](https://insights.sbomify.com/CVE-2022-42968/): Gitea vulnerable to Argument Injection (critical 9.8)
- [CVE-2021-45330](https://insights.sbomify.com/CVE-2021-45330/): Improper Privilege Management in Gitea (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70357 is a high-severity server-side request forgery vulnerability in Gitea Gitea, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70357 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitea (Bitnami): affected all versions; fixed in 28.0.0

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

## Sources

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

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