Gitea · Gitea · published 2026-10-06
CVE-2026-70357Gitea repository migration SSRF through DNS rebinding
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-70357 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 31% of all CVEs. This Gitea vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Gitea 28.1.0, 28.0.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.1.0, 28.0.0.
Patch events
DevOpsGitea
Gitea security releases: 28.1.0, 28.0.0
Upgrade to
28.1.028.0.0Why: CVE-2026-89182: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (31th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
0through1.27.3(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.