CVE-2026-94205

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th 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-93919 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For pull_request activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-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.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 6, 2026

Last Modified

October 13, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
Patch available. Sources: github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Gitea Actions: fork pull request approval bypass via maintainer-triggered pull_request sub-events (ifNeedApprovalWith keys on the event actor, not the pull request author) · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp
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
GitHub pull request

fix(actions): harden fork pull request run approval

Fix merged in go-gitea/gitea PR #39399 on 2026-09-26 — awaiting tagged release

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

Gitea 28.0.0 is released | Gitea Blog

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 63× 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:36 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-01 13:59 UTCEG score recompute
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-31 13:15 UTCEG score recompute
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-30 12:28 UTCEG score recompute
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-29 11:46 UTCEG score recompute
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-28 11:03 UTCEG score recompute
  11. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-10-27 09:29 UTCEG score recompute
  13. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-26 08:47 UTCEG score recompute
  15. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-25 13:49 UTCEG score recompute
  17. 2026-10-25 08:03 UTCEG score recompute
  18. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-24 07:20 UTCEG score recompute
  20. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-23 06:37 UTCEG score recompute
  22. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-22 05:50 UTCEG score recompute
  24. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-21 05:05 UTCEG score recompute
Show 38 more
  1. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-20 04:21 UTCEG score recompute
  3. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-19 03:36 UTCEG score recompute
  5. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  6. 2026-10-18 02:58 UTCEG score recompute
  7. 2026-10-18 02:52 UTCEG score recompute
  8. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-17 02:09 UTCEG score recompute
  10. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-16 01:25 UTCEG score recompute
  12. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-14 20:55 UTCEG score recompute
  14. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-13 16:47 UTCEG score recompute
  16. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-12 21:32 UTCEG score recompute
  18. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-12 14:42 UTCEG score recompute
  20. 2026-10-11 19:12 UTCEG score recompute
  21. 2026-10-11 16:27 UTCEG score recompute
  22. 2026-10-11 15:14 UTCEG score recompute
  23. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-11 13:41 UTCEG score recompute
  25. 2026-10-11 11:32 UTCEG score recompute
  26. 2026-10-10 20:41 UTCEG score recompute
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  28. 2026-10-09 22:28 UTCEG score recompute
  29. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-10-08 19:46 UTCEG score recompute
  31. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  32. 2026-10-08 01:08 UTCEG score recompute
  33. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-10-07 20:22 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  35. 2026-10-07 20:21 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  36. 2026-10-06 20:31 UTCNVD update
  37. 2026-10-06 19:32 UTCEG score recompute
  38. 2026-10-06 19:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-94205?
CVE-2026-94205 is a critical-severity vulnerability; its CVE record was published on October 6, 2026. Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For pull_request activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval,…
When was the CVE record for CVE-2026-94205 published?
The CVE record for CVE-2026-94205 was published on October 6, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-94205 actively exploited?
CVE-2026-94205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94205?
CVE-2026-94205 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-94205?
A fix for CVE-2026-94205 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-94205

Explore →

Is Your Infrastructure Affected by CVE-2026-94205?

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