Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs processes attacker-controlled data from the /ext URL route in yamcs-web/src/main/webapp/projects/webapp/src/app/core/routes/extension.matcher.ts, extension.component.ts, and app.component.ts without checking registered plugin IDs before DOM rendering through innerHTML. A crafted URL can execute JavaScript when opened by a user. The script can read data available to the Yamcs web application and perform actions in the user context. This issue is fixed in versions 5.12.8 and 5.13.2.
CVE-2026-55566
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3MEDIUMmedium confidence
- EG Risk
- 35EG Risk 35/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)Severity43% × 45%The EG Score, 4.3 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.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 public PoC (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.4%
- EPSS %ILE
- 30th
- 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 public PoC (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.
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
August 28, 2026
Last Modified
September 8, 2026
Advisory Details (5)
Auto-updated Aug 28, 2026DOM XSS in Extension Routing · Advisory · yamcs/yamcs · GitHub
https://github.com/yamcs/yamcs/security/advisories/GHSA-9272-wg2r-7xmxYamcs 5.13.2
Patch available: yamcs/yamcs yamcs-5.13.2
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2Yamcs 5.12.8
Patch available: yamcs/yamcs yamcs-5.12.8
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8commit ecf34a4e2ccb (yamcs/yamcs)
Fix landed in yamcs/yamcs commit ecf34a4e2ccb — awaiting tagged release
https://github.com/yamcs/yamcs/commit/ecf34a4e2ccbe085e6ceff0253595b24d5ecb4aacommit 8e18e279d8ce (yamcs/yamcs)
Fix landed in yamcs/yamcs commit 8e18e279d8ce — awaiting tagged release
https://github.com/yamcs/yamcs/commit/8e18e279d8ce761c21f4f67bbd06a1bff804d297Vendor Advisories for CVE-2026-55566(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.yamcs:yamcs-core | 0.29.3 ... 5.9.9 (166 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 53× 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-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 15:55 UTCEG score recompute
- 2026-10-11 19:39 UTCEG score recompute
- 2026-10-11 16:54 UTCEG score recompute
- 2026-10-11 14:17 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-10 00:53 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-09 02:38 UTCEG score recompute
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-08 00:51 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-06 23:00 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-06 00:48 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-05 01:20 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-04 02:43 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-03 04:29 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-02 06:16 UTCEG score recompute
Show 58 moreShow fewer
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-01 07:49 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-30 09:36 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-29 11:10 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-27 14:23 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-26 15:34 UTCEG score recompute
- 2026-09-24 15:23 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-22 18:43 UTCEG score recompute
- 2026-09-20 22:05 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-19 23:51 UTCEG score recompute
- 2026-09-19 01:38 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-18 03:25 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-17 05:12 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-16 06:58 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-15 08:45 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-14 10:29 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-13 12:16 UTCEG score recompute
- 2026-09-11 15:50 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-10 17:37 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-09 19:24 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-08 03:54 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-07 05:41 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-06 07:27 UTCEG score recompute
- 2026-09-05 09:12 UTCEG score recompute
- 2026-09-04 10:59 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-02 14:24 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-01 16:07 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-31 17:29 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-30 19:13 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-08-28 22:45 UTCEG score recompute
- 2026-08-28 22:09 UTCEG score recompute
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 18:10 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
Related CVEs(same product + same CWE)
Same product
10 shownMaven:org.yamcs:yamcs-core
Frequently asked(5)
What is CVE-2026-55566?
When was the CVE record for CVE-2026-55566 published?
Is CVE-2026-55566 actively exploited?
What is the CVSS score of CVE-2026-55566?
How do I remediate CVE-2026-55566?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55566
Is Your Infrastructure Affected by CVE-2026-55566?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.