CVE-2026-70357

Undergoing Analysis Undergoing Analysis - In Progress

BaseFortify

Publication date: 2026-10-06

Last updated on: 2026-10-13

Assigner: Gitea Limited

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-06

Last Modified

2026-10-13

Generated

2026-10-19

AI Q&A

2026-10-07

EPSS Evaluated

2026-10-18

NVD

CVE-2026-70357

EUVD

EUVD-2026-93917

Affected Vendors & Products

Vendor	Product	Version / Range
gitea	gitea	to 28.0.0 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

This vulnerability in Gitea involves a mismatch between hostname validation and actual connection behavior during repository migration. Gitea checks if a migration hostname is allowed or blocked before starting Git, but Git independently resolves the hostname when connecting. An attacker can exploit this by controlling the destination's DNS to change the resolved address between validation and connection, bypassing blocked internal addresses.

Detection Guidance

This vulnerability involves Git subprocess hostname resolution bypassing Gitea's validation. Detect it by monitoring Git clone operations during repository migrations and checking for DNS changes between validation and connection. Inspect Gitea logs for migration attempts and verify if Git subprocesses connect to unexpected internal addresses.

Impact Analysis

If you use Gitea for repository migrations, an attacker could trick Gitea into connecting to an unintended internal address by manipulating DNS. This could lead to unauthorized access to internal systems or data exfiltration, depending on the attacker's goals and the network configuration.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. Organizations using Gitea may face compliance risks if attackers exploit this to access protected health information or personal data.

Mitigation Strategies

Immediately update Gitea to the latest patched version. Restrict internal network access to Gitea instances and block unauthorized DNS resolution changes. Monitor Git clone operations during migrations and audit migration logs for suspicious activity.

Hi! I’m here to help you understand CVE-2026-70357. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70