Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs WebSocket subscription handlers fail to enforce the privileges required by equivalent REST endpoints. PacketsApi.subscribePackets exposes the packets WebSocket topic without ObjectPrivilegeType.ReadPacket, ProcessingApi.subscribeAlgorithmStatus exposes the algorithm-status WebSocket topic without ObjectPrivilegeType.ReadAlgorithm, and MdbOverrideApi.subscribeMdbChanges exposes the mdb-changes WebSocket topic without SystemPrivilege.GetMissionDatabase. A low-privilege authenticated user can receive telemetry packets, algorithm status, and mission database change information outside the assigned authorization scope. This issue is fixed in versions 5.12.8 and 5.13.2.
CVE-2026-55545
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMmedium confidence
- EG Risk
- 29EG Risk 29/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)Severity65% × 45%The EG Score, 6.5 of 10.Exploitation0.4% × 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.5%
- EPSS %ILE
- 37th
- KEV
- Not listed
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.
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, 2026WebSocket subscription handlers omit the privilege checks their REST siblings enforce · Advisory · yamcs/yamcs · GitHub
https://github.com/yamcs/yamcs/security/advisories/GHSA-fwww-cp23-7f5gYamcs 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 12864af555e6 (yamcs/yamcs)
Fix landed in yamcs/yamcs commit 12864af555e6 — awaiting tagged release
https://github.com/yamcs/yamcs/commit/12864af555e6ca4941b01c1f1217859cc0492ce0commit 0691731846c5 (yamcs/yamcs)
Fix landed in yamcs/yamcs commit 0691731846c5 — awaiting tagged release
https://github.com/yamcs/yamcs/commit/0691731846c5a0aca81b88fabbd2cd51d56fe076Vendor Advisories for CVE-2026-55545(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 | 5.13.0, 5.13.1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× 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.5% · 37th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 37th 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.5% · 37th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-10 05:16 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-09 02:39 UTCEG score recompute
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-07 09:50 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-06 07:27 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-05 04:40 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-04 02:37 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
- 2026-10-03 00:34 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-10-01 22:31 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 36th percentile
Show 56 moreShow fewer
- 2026-09-30 19:49 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-29 14:13 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-28 12:10 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-27 10:07 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-26 08:04 UTCEG score recompute
- 2026-09-25 04:36 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 36th percentile
- 2026-09-24 02:34 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-23 00:31 UTCEG score recompute
- 2026-09-21 22:28 UTCEG score recompute
- 2026-09-20 20:26 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-19 18:23 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-18 16:21 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-17 14:18 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-16 12:13 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-15 10:10 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-14 08:04 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-13 06:02 UTCEG score recompute
- 2026-09-12 04:00 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-11 01:56 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-09 23:52 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-08 10:23 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-07 08:03 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-06 05:45 UTCEG score recompute
- 2026-09-05 03:43 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-02 23:37 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-01 21:34 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-31 19:31 UTCEG score recompute
- 2026-08-31 19:08 UTCEG score recompute
- 2026-08-31 00:30 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 18:11 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
Related CVEs(same product + same CWE)
Same product
10 shownMaven:org.yamcs:yamcs-core
Frequently asked(5)
What is CVE-2026-55545?
When was the CVE record for CVE-2026-55545 published?
Is CVE-2026-55545 actively exploited?
What is the CVSS score of CVE-2026-55545?
How do I remediate CVE-2026-55545?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55545
Is Your Infrastructure Affected by CVE-2026-55545?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.