CVE-2026-89430

HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.1 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).

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

A fix is available — apply it.

Gitea validated a push mirror's remote address against the [migrations] allow and block lists only when the mirror was created. Each synchronization passed the stored address directly to git push, so a name that later resolved to a blocked or internal address was still reached. A user with administrator access to a repository, which includes repositories they create themselves, could aim push mirror synchronization at internal Git services and force-push the repository's contents to them.

CVSS v3
8.1
EG Score
8.1HIGHlow confidence
EG Risk
36
EG Risk 36/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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, 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
github_pr

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

Gitea Push Mirror Host Policy Bypass Enables SSRF and Forced Writes to Internal Git Repositories · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-hcgw-r9gf-8mph

Weakness Classification(2)

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.

  1. 2026-10-07 20:22 UTCEG score recompute▲ 8.10
  2. 2026-10-07 20:21 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  3. 2026-10-06 20:31 UTCNVD update
  4. 2026-10-06 19:33 UTCEG score recompute
  5. 2026-10-06 19:31 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89430?
CVE-2026-89430 is a high vulnerability published on October 6, 2026. Gitea validated a push mirror's remote address against the [migrations] allow and block lists only when the mirror was created. Each synchronization passed the stored address directly to git push, so a name that later resolved to a blocked or internal address was still reached. A user with…
When was CVE-2026-89430 disclosed?
CVE-2026-89430 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.
What is the CVSS score of CVE-2026-89430?
CVE-2026-89430 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-89430?
A fix for CVE-2026-89430 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-89430

Explore →

Is Your Infrastructure Affected by CVE-2026-89430?

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