CVE-2026-70400

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS

Also known asEUVD-2026-101094 (ENISA EUVD)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate only on public resources can create a private repository and migration task under the authorizing account or an organization where that user has the necessary permissions. The ordinary private repository-creation route rejects the same token, but the migration path omits that restriction.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

October 14, 2026

Advisory Details (4)

Auto-updated Oct 14, 2026
Fix referenced — no release confirmed yet. Sources: github_pr, github.
GitHub advisoryMentions a patch (unverified)

Repository migration skips public-only token guard for private repository creation · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-x58h-3mx5-q44r
GitHub pull request

fix(api): enforce repository creation token authorization (#39007)

Fix merged in go-gitea/gitea PR #39014 on 2026-08-21 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/39014
GitHub pull request

fix(api): enforce repository creation token authorization

Fix merged in go-gitea/gitea PR #39007 on 2026-08-21 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/39007
Web page

Gitea 1.27.3 is released | Gitea Blog

https://blog.gitea.com/release-of-1.27.3/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-27 13:25 UTCOSV refresh
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-25 14:08 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-18 03:18 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-14 16:29 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  23. 2026-10-14 16:25 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  24. 2026-10-14 15:35 UTCEG score recompute
  25. 2026-10-14 15:25 UTCNVD update
Show 3 more
  1. 2026-10-14 15:24 UTCMITRE cvelistV5CVSS v3 → 5.4 · severity → MEDIUM
  2. 2026-10-14 14:41 UTCEG score recompute
  3. 2026-10-14 14:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-70400?
CVE-2026-70400 is a medium-severity vulnerability; its CVE record was published on October 14, 2026. Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate only on public resources can create a private repository and migration task under the authorizing account or an organization where that…
When was the CVE record for CVE-2026-70400 published?
The CVE record for CVE-2026-70400 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-70400 actively exploited?
CVE-2026-70400 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70400?
CVE-2026-70400 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-70400?
A fix for CVE-2026-70400 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-70400?

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