CVE-2026-116474

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th 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-114796 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The GITEA_TOKEN of a Gitea Actions job authenticates as the gitea-actions system user, and the /api/v1/user email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the address is stored as activated. Commit verification treats a key without a real owner as the instance signing key, so any user who can run a workflow job could make commits signed with their own key show as trusted and signed by the instance in every repository where they appear, including pull requests to repositories the user cannot write to. The impact is limited to the displayed signature status: enforcement such as required signed commits only checks that a signature is verified and is unaffected, and no access is gained. The /api/v1/user routes now reject system users.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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 available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 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.2% within 30 daysSource: FIRST EPSS. 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.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 available. Apply it within your standard update timelines.

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.

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

November 1, 2026

Last Modified

November 6, 2026

Advisory Details (5)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_pr, github_release.
GitHub release Patch Available

v28.3.0

Patch available: go-gitea/gitea v28.3.0

https://github.com/go-gitea/gitea/releases/tag/v28.3.0
Web page

Gitea 28.3.0 is released | Gitea Blog

https://blog.gitea.com/release-of-28.3.0/
GitHub pull request

fix: harden context user access scope (#39945)

Fix merged in go-gitea/gitea PR #40115 on 2026-10-31 — awaiting tagged release

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

fix: harden context user access scope

Fix merged in go-gitea/gitea PR #39945 on 2026-10-31 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/39945
GitHub advisoryMentions a patch (unverified)

Actions token can spoof instance-signed commits by adding a GPG key · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-mf6p-vqpw-3r7x

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 16× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-11-06 15:38 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  9. 2026-11-06 15:37 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  10. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-11-01 11:02 UTCENISA EUVD ID recordedEUVD-2026-114796 · Source: ENISA EUVD
  16. 2026-11-01 10:26 UTCNVD update
  17. 2026-11-01 09:52 UTCEchelonGraph re-scored
  18. 2026-11-01 09:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-116474?
CVE-2026-116474 is a medium-severity vulnerability; its CVE record was published on November 1, 2026. The GITEA_TOKEN of a Gitea Actions job authenticates as the gitea-actions system user, and the /api/v1/user email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the address is stored as…
When was the CVE record for CVE-2026-116474 published?
The CVE record for CVE-2026-116474 was published on November 1, 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 November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-116474 actively exploited?
CVE-2026-116474 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-116474?
CVE-2026-116474 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-116474?
A fix for CVE-2026-116474 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-116474

Explore →

Is Your Infrastructure Affected by CVE-2026-116474?

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

Book a Demo →Browse All CVEs