CVE-2026-101027

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 4 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When [migrations] ALLOWED_DOMAINS was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it resolve to loopback or private addresses and bypass ALLOW_LOCALNETWORKS = false, reaching internal services from the Gitea server. Instances without ALLOWED_DOMAINS configured are not affected by this specific bypass.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/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 computed
Severity77% × 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
0.2%
EPSS %ILE
5th
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 (4)

Auto-updated Oct 7, 2026
Patch available. Sources: github, github_pr, github_release.
github_release Patch Available

v28.0.0

Patch available: go-gitea/gitea v28.0.0

https://github.com/go-gitea/gitea/releases/tag/v28.0.0
generic

Gitea 28.0.0 is released | Gitea Blog

https://blog.gitea.com/release-of-28.0.0/
github_pr

fix(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/39426
githubMentions a patch (unverified)

SSRF via DNS rebinding: MatchHostOrIP short-circuits IP check when hostname matches ALLOWED_DOMAINS · Advisory · go-gitea/gitea · GitHub

Affected: v1.26.2

https://github.com/go-gitea/gitea/security/advisories/GHSA-fqjr-23c8-gg9m

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× 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.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-09 04:49 UTCEG score recompute
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-08 04:46 UTCEG score recompute
  5. 2026-10-07 23:47 UTCEPSS rescore
  6. 2026-10-07 11:47 UTCEG score recompute▲ 7.70
  7. 2026-10-07 11:46 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  8. 2026-10-06 20:31 UTCNVD update
  9. 2026-10-06 19:33 UTCEG score recompute
  10. 2026-10-06 19:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-101027?
CVE-2026-101027 is a high vulnerability published on October 6, 2026. When [migrations] ALLOWEDDOMAINS was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it resolve to loopback or…
When was CVE-2026-101027 disclosed?
CVE-2026-101027 was first published on October 6, 2026, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101027 actively exploited?
CVE-2026-101027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101027?
CVE-2026-101027 has a CVSS v3.1 base score of 7.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-101027?
A fix for CVE-2026-101027 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-101027

Explore →

Is Your Infrastructure Affected by CVE-2026-101027?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.