SkillHub before 0.2.22 contains an incorrect authorization vulnerability in AccountMergeService and AccountMergeController that allows authenticated attackers to take over other accounts by abusing the merge flow. Attackers can call the merge initiate endpoint with a target username or OAuth identity, receive the verification token directly, and confirm the merge to inherit the victim's API tokens, roles and namespace ownership.
CVE-2026-108550
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-10. A secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 40EG 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
- 21st
- 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 10, 2026
Last Modified
October 10, 2026
Advisory Details (5)
Auto-updated Oct 10, 2026SkillHub before 0.2.22 Account Takeover via Account Merge Flow | Advisories | VulnCheck
https://www.vulncheck.com/advisories/skillhub-before-0.2.22-account-takeover-via-account-merge-flowSkillHub v0.2.22
Patch available: iflytek/skillhub v0.2.22
https://github.com/iflytek/skillhub/releases/tag/v0.2.22commit 45228996c7dd (iflytek/skillhub)
Patch available: iflytek/skillhub v0.2.22 (contains commit 45228996c7dd)
https://github.com/iflytek/skillhub/commit/45228996c7dd67f9304dba5b221fef15138a7fc4GitHub - iflytek/skillhub: Self-hosted, open-source agent skill registry for enterprises. Publish & version skill packages, govern with RBAC and audit logs, deploy on-premise with Docker or Kubernetes. · GitHub
https://github.com/iflytek/skillhubAccount merge flow lets any authenticated user take over any other account (verification token returned to the wrong party) · Issue #921 · iflytek/skillhub · GitHub
https://github.com/iflytek/skillhub/issues/921Vendor Advisories for CVE-2026-108550(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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.
- 2026-10-11 20:13 UTCEG score recompute
- 2026-10-11 17:54 UTCEG score recompute
- 2026-10-11 17:54 UTCGHSA enrichmentGHSA-wq7r-c6mg-rqv2 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-11 14:59 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-11 04:41 UTCEG score recompute
- 2026-10-11 04:40 UTCGHSA enrichmentGHSA-wq7r-c6mg-rqv2 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-10-10 15:30 UTCEG score recompute
- 2026-10-10 14:45 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-10-10 14:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108550?
When was CVE-2026-108550 made public?
Is CVE-2026-108550 actively exploited?
What is the CVSS score of CVE-2026-108550?
How do I remediate CVE-2026-108550?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108550
Is Your Infrastructure Affected by CVE-2026-108550?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.