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.
CVE-2026-101029
This medium-severity CVE scores 4.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3MEDIUMlow confidence
- EG Risk
- 19EG Risk 19/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 7, 2026
Advisory Details (5)
Auto-updated Oct 7, 2026v28.0.0
Patch available: go-gitea/gitea v28.0.0
https://github.com/go-gitea/gitea/releases/tag/v28.0.0fix(git)!: use internal proxy for all git operations
Fix merged in go-gitea/gitea PR #39426 on 2026-09-29 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/39426fix: classify git failures on stderr, restrict migration failure detail
Fix merged in go-gitea/gitea PR #39010 on 2026-09-15 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/39010Migration / pull-mirror SSRF, egress allow-list bypass via multi-answer DNS - 3 findings · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-6g2h-xpg3-rm48Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-07 20:36 UTCEG score recompute▲ 4.30
- 2026-10-07 20:36 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
- 2026-10-06 20:31 UTCNVD update
- 2026-10-06 19:33 UTCEG score recompute
- 2026-10-06 19:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-101029?
When was CVE-2026-101029 disclosed?
What is the CVSS score of CVE-2026-101029?
How do I remediate CVE-2026-101029?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-101029
Is Your Infrastructure Affected by CVE-2026-101029?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.