CVE-2026-101029

What it is

Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns multiple DNS answers, because the address that was validated was not necessarily the address Git later connected to. A low-privileged user who can create migrations or mirrors could direct the server to internal services, reading from and writing to reachable internal Git or HTTP endpoints. Content from internal responses could additionally be disclosed through migration and mirror error messages.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-06 20:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-15 02:29 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-10-06 20:17 UTC

Last modified

2026-10-15 02:29 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-209

Record status

Analyzed

Affected

• Gitea < 28.0.0

Attack profile CVSS 3.1 · 4.3

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-101029.md and follow it. Check whether this project is affected by CVE-2026-101029. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge