CVE-2026-70357

Gitea repository migration SSRF through DNS rebinding

Published Oct 6, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Gitea validates a repository migration hostname against its allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker with the ability to start a migration can control the destination's DNS and modify the address after validation but before the Git connection, enabling the subprocess to reach blocked internal addresses. This results in a server‑side request forgery that exposes internal network resources. The flaw is a DNS rebinding vulnerability classified as CWE‑918 and does not provide remote code execution; the impact is limited to SSRF and potential internal reconnaissance.

Affected Systems

The CVE data lists the affected vendor and product as Gitea Gitea, but does not enumerate specific versions. Therefore only installations that run Gitea and enable external repository migrations via the Git clone operation are potentially vulnerable. The exact version range is not provided, so a vendor‑specific update should be applied once available.

Risk and Exploitability

The EPSS score of < 1% and the flaw is not listed in the CISA KEV catalog. The CVSS score of 7.5 indicates a high severity. Based on the description, it is inferred that the likely attack vector is remote over the web, making the vulnerability readily exploitable by a wide range of threat actors.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Gitea version 28.0.0 or later, which resolves the race condition between validation and DNS resolution.
  • Disable external migrations or limit allowed hosts in the Gitea configuration so that only trusted URLs can be used for migrations.
  • Block the Gitea server’s DNS resolution for internal IP ranges at the network level or using a reverse proxy so that the Git subprocess cannot reach internal addresses during a migration.

Generated by OpenCVE AI on October 7, 2026 at 22:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
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.
Title Gitea repository migration SSRF through DNS rebinding
Weaknesses CWE-918
References
Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 8:12 PM
Reserved
Aug 13, 2026, 4:50 PM
Status
Analyzed
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 13, 2026, 5:16 PM