{"id":"CVE-2026-55545","aliases":["EUVD-2026-67839","GHSA-fwww-cp23-7f5g"],"status":"published","title":"Yamcs: WebSocket subscription handlers omit the privilege checks their REST siblings enforce","description":"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.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00451,"percentile":0.39489,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-862"],"published":"2026-08-28T17:09:53Z","modified":"2026-10-28T11:14:56Z","fixes":[{"ecosystem":"Maven","package":"org.yamcs:yamcs-core","fixed_in":["5.12.8","5.13.2"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.yamcs:yamcs-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"5.12.7"},{"fixed":"5.12.8"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.yamcs:yamcs-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.13.0"},{"last_affected":"5.13.1"},{"fixed":"5.13.2"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.yamcs:yamcs-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.12.8"}]}],"versions":["0.29.3","0.30.0","3.0.0","3.1.0","3.1.1","3.1.2","3.2.0","3.2.1","3.2.2","3.3.0","3.3.1","3.4.0","3.4.1","3.4.11","3.4.2","3.4.3","3.4.4","3.4.5","3.4.6","3.4.8","4.0.0","4.0.1","4.1.1","4.1.2","4.10.0","4.10.1","4.10.2","4.10.3","4.10.4","4.10.5","4.10.6","4.10.7","4.10.8","4.10.9","4.2.0","4.2.1","4.2.2","4.3.0","4.3.1","4.4.0","4.4.1","4.4.2","4.5.0","4.6.0","4.6.1","4.6.2","4.6.3","4.7","4.7.1","4.7.3","4.8.0","4.8.1","4.9.0","4.9.1","4.9.2","4.9.3","4.9.4","5.0.0","5.1.0","5.1.1","5.1.2","5.1.3","5.1.4","5.10.0","5.10.1","5.10.10","5.10.11","5.10.12","5.10.2","5.10.3","5.10.4","5.10.5","5.10.6","5.10.7","5.10.8","5.10.9","5.11.0","5.11.1","5.11.10","5.11.11","5.11.12","5.11.13","5.11.2","5.11.3","5.11.4","5.11.5","5.11.6","5.11.7","5.11.8","5.11.9","5.12.0","5.12.1","5.12.2","5.12.3","5.12.4","5.12.5","5.12.6","5.12.7","5.2.0","5.2.1","5.2.2","5.2.3","5.2.4","5.2.5","5.2.6","5.3.0","5.3.1","5.3.2","5.3.3","5.3.4","5.3.5","5.3.6","5.4.0","5.4.1","5.4.2","5.4.3","5.4.4","5.4.5","5.5.0","5.5.1","5.5.2","5.5.3","5.5.4","5.5.5","5.5.6","5.5.7","5.6.0","5.6.1","5.6.2","5.7.0","5.7.1","5.7.10","5.7.11","5.7.12","5.7.13","5.7.2","5.7.3","5.7.4","5.7.5","5.7.6","5.7.7","5.7.8","5.7.9","5.8.0","5.8.1","5.8.2","5.8.3","5.8.4","5.8.5","5.8.6","5.8.7","5.8.8","5.9.0","5.9.1","5.9.10","5.9.11","5.9.12","5.9.2","5.9.3","5.9.4","5.9.5","5.9.6","5.9.7","5.9.8","5.9.8.1","5.9.9"]},{"source":"osv","ecosystem":"Maven","package":"org.yamcs:yamcs-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.13.0"},{"fixed":"5.13.2"}]}],"versions":["5.13.0","5.13.1"]}],"products":[{"vendor":"yamcs","product":"yamcs"}],"references":[{"url":"https://github.com/yamcs/yamcs/security/advisories/GHSA-fwww-cp23-7f5g","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/yamcs/yamcs/commit/0691731846c5a0aca81b88fabbd2cd51d56fe076","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/yamcs/yamcs/commit/12864af555e6ca4941b01c1f1217859cc0492ce0","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/advisories/GHSA-fwww-cp23-7f5g"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55545.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55545","tags":["advisory"]},{"url":"https://github.com/yamcs/yamcs","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-55545","title":"Yamcs: WebSocket subscription handlers omit the privilege checks their REST siblings enforce","description":"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.","status":"published","published":"2026-08-28T17:09:53.114Z","modified":"2026-08-31T18:55:41.849Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T14:20:11.925815Z"}],"euvd":[{"id":"EUVD-2026-67839","description":"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.","status":"published","published":"2026-08-28T17:09:53Z","modified":"2026-08-31T18:55:41Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T18:01:19.818565Z"}],"ghsa":[{"id":"GHSA-fwww-cp23-7f5g","title":"Yamcs's WebSocket subscription handlers omit the privilege checks their REST siblings enforce","description":"**Asset / scope:** Yamcs 5.12.7 WebSocket topics (`packets`, `algorithm-status`, `mdb-changes`)\n\n## Summary\n\nSeveral WebSocket subscription handlers do not perform the privilege check that their REST counterparts\nenforce, so a principal subscribing over WebSocket receives data the REST API would have scoped or denied.\n\n## Root cause\n\n- `packets` (`PacketsApi.subscribePackets`) performs no `ReadPacket` check, while the REST siblings do\n  (`listPackets:128`, `streamPackets:256`, `subscribeContainers:538`). A principal with a narrow\n  `ReadPacket` scope receives the raw binary of all TM packets on the processor.\n- `algorithm-status` (`ProcessingApi.subscribeAlgorithmStatus`) performs no check, while REST\n  `getAlgorithmStatus` enforces `checkObjectPrivileges(ReadAlgorithm, ...)` (`:467`).\n- `mdb-changes` (`MdbOverrideApi.subscribeMdbChanges`) performs no check, while base MDB reads require\n  `GetMissionDatabase`.\n\n## Remediation\n\nBring each WebSocket subscription handler to parity with its REST sibling's privilege check\n(`ReadPacket`, `ReadAlgorithm`, `GetMissionDatabase`). This is the same declarative fail-closed fix as\nReport 1.\n\n## Supporting material\n\nSubsystem source audit of the WS-vs-REST authorization parity. Available on request.\n\n--\n\n## Disclosure and credit\n\nThis was found by Cipher / Causal Security - https://causalsecurity.com/. We are coordinating disclosure\nvia this report and request CVEs where you agree they qualify. We propose the 90-day window stated in your\nsecurity policy. We might publish a write-up after a fix and the agreed window.","status":"published","published":"2026-08-28T17:10:26Z","modified":"2026-08-28T17:10:27Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T14:41:07.031507Z"}],"nvd":[{"id":"CVE-2026-55545","description":"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.","status":"published","published":"2026-08-28T20:18:28.38Z","modified":"2026-09-08T21:08:37.32Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T14:12:42.366888Z"}],"osv":[{"id":"CVE-2026-55545","title":"Yamcs: WebSocket subscription handlers omit the privilege checks their REST siblings enforce","description":"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.","status":"published","published":"2026-08-28T17:09:53.114Z","modified":"2026-10-28T11:14:56.514632099Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T15:45:11.22012Z"},{"id":"GHSA-fwww-cp23-7f5g","title":"Yamcs's WebSocket subscription handlers omit the privilege checks their REST siblings enforce","description":"**Asset / scope:** Yamcs 5.12.7 WebSocket topics (`packets`, `algorithm-status`, `mdb-changes`)\n\n## Summary\n\nSeveral WebSocket subscription handlers do not perform the privilege check that their REST counterparts\nenforce, so a principal subscribing over WebSocket receives data the REST API would have scoped or denied.\n\n## Root cause\n\n- `packets` (`PacketsApi.subscribePackets`) performs no `ReadPacket` check, while the REST siblings do\n  (`listPackets:128`, `streamPackets:256`, `subscribeContainers:538`). A principal with a narrow\n  `ReadPacket` scope receives the raw binary of all TM packets on the processor.\n- `algorithm-status` (`ProcessingApi.subscribeAlgorithmStatus`) performs no check, while REST\n  `getAlgorithmStatus` enforces `checkObjectPrivileges(ReadAlgorithm, ...)` (`:467`).\n- `mdb-changes` (`MdbOverrideApi.subscribeMdbChanges`) performs no check, while base MDB reads require\n  `GetMissionDatabase`.\n\n## Remediation\n\nBring each WebSocket subscription handler to parity with its REST sibling's privilege check\n(`ReadPacket`, `ReadAlgorithm`, `GetMissionDatabase`). This is the same declarative fail-closed fix as\nReport 1.\n\n## Supporting material\n\nSubsystem source audit of the WS-vs-REST authorization parity. Available on request.\n\n--\n\n## Disclosure and credit\n\nThis was found by Cipher / Causal Security - https://causalsecurity.com/. We are coordinating disclosure\nvia this report and request CVEs where you agree they qualify. We propose the 90-day window stated in your\nsecurity policy. We might publish a write-up after a fix and the agreed window.","status":"published","published":"2026-08-28T17:10:26Z","modified":"2026-08-28T17:25:37.21366Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T15:46:47.119724Z"}]}}