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.

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.

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.