CVE-2026-55521High· 8.8▾ TwilightYamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs omits authorization checks in IndexesApi.listPacketIndex, IndexesApi.listEventIndex, Cop1Api.disable, Cop1Api.resume, Cop1Api.initialize, Cop1Api.updateConfig, and T…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Aug 29.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
0.4%
Last analysed / modified upstream
Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs omits authorization checks in IndexesApi.listPacketIndex, IndexesApi.listEventIndex, Cop1Api.disable, Cop1Api.resume, Cop1Api.initialize, Cop1Api.updateConfig, and TimeApi.setTime. An authenticated low-privilege user can read packet and event index metadata without ObjectPrivilegeType.ReadPacket, alter COP-1 link state without SystemPrivilege.ControlLinks, and manipulate simulation time. These operations can disclose telemetry metadata, disrupt telecommand handling, and affect system integrity and availability. This issue is fixed in versions 5.12.8 and 5.13.2.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Affected packages:
org.yamcs:yamcs-core >= 5.13.0, <= 5.13.1org.yamcs:yamcs-core <= 5.12.7Patched in:
org.yamcs:yamcs-core 5.13.2org.yamcs:yamcs-core 5.12.8Connected by shared product, vendor, weakness, or advisory.
CVE-2026-55545Medium· 6.5Yamcs is a mission control framework
CVE-2026-55547Medium· 4.3Yamcs is a mission control framework
CVE-2026-55559Critical· 9.8Yamcs is a mission control framework
CVE-2026-55565Critical· 9.9Yamcs is a mission control framework
CVE-2026-55566Medium· 4.3Yamcs is a mission control framework
CVE-2026-55511Critical· 9.1Yamcs is a mission control framework