CVE-2026-104632

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th 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
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the repository's runners without an explicit approval.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.3% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 7, 2026

Advisory Details (4)

Auto-updated Oct 7, 2026
Patch available. Sources: github_pr, github_release, github.
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
Web page

Gitea 28.0.0 is released | Gitea Blog

https://blog.gitea.com/release-of-28.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
GitHub advisoryMentions a patch (unverified)

Untrusted first-time fork PR achieves self-hosted Actions runner RCE without approval via cancel-then-rerun · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-pvjf-7jrm-6w9g

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 17× 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-10-11 20:15 UTCEG score recompute
  2. 2026-10-11 18:27 UTCEG score recompute
  3. 2026-10-11 15:01 UTCEG score recompute
  4. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-11 02:27 UTCEG score recompute
  6. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-10 00:43 UTCEG score recompute
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-08 23:03 UTCEG score recompute
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-08 10:15 UTCEG score recompute
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-07 20:36 UTCEG score recomputeFirst assessed: 8.8 HIGH
  14. 2026-10-07 20:36 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  15. 2026-10-06 20:31 UTCNVD update
  16. 2026-10-06 19:33 UTCEG score recompute
  17. 2026-10-06 19:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-104632?
CVE-2026-104632 is a high-severity vulnerability; its CVE record was published on October 6, 2026. Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access…
When was the CVE record for CVE-2026-104632 published?
The CVE record for CVE-2026-104632 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 7, 2026; the record at its source may have been updated since.
Is CVE-2026-104632 actively exploited?
CVE-2026-104632 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104632?
CVE-2026-104632 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-104632?
A fix for CVE-2026-104632 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-104632

Explore →

Is Your Infrastructure Affected by CVE-2026-104632?

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