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.
Published: 2026-08-28
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability causes Yamcs WebSocket subscription handlers to bypass the privilege checks that are enforced by their REST counterparts. The missing checks allow a logged‑in user with minimal privileges to receive telemetry packets, algorithm status updates, and mission database change notifications that the user is not authorized to view. This results in the unintended disclosure of sensitive operational data. The weakness is a classic example of missing access control (CWE‑862).

Affected Systems

Yamcs versions prior to 5.12.8 and before 5.13.2 are affected. These releases lack the privilege enforcement that newer 5.12.8 and 5.13.2 patches add. Administrators should verify the current deployment against the version list and treat any older build as vulnerable.

Risk and Exploitability

The CVSS score of 6.5 denotes moderate severity. No EPSS data is available, so the publicly reported exploitation probability is unknown. The issue is not listed in the CISA KEV catalog, suggesting no confirmed large‑scale exploitation yet. The attack requires an authenticated network connection to a Yamcs instance over WebSocket; the vulnerability is therefore exploitable by any user with an account, provided they request a subscription. The likely vector is remote network access to the WebSocket endpoint, implying that the threat is primarily in controlled site or open internet environments.

Generated by OpenCVE AI on August 28, 2026 at 20:56 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Yamcs to version 5.12.8 or later 5.13.2 to enforce privilege checks in WebSocket subscriptions
  • Re‑evaluate user privileges and remove any unnecessary permissions, especially on accounts that may subscribe to sensitive topics
  • Test the subscription endpoints with a low‑privilege account to confirm that privilege checks now block unauthorized data streams

Generated by OpenCVE AI on August 28, 2026 at 20:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-fwww-cp23-7f5g Yamcs's WebSocket subscription handlers omit the privilege checks their REST siblings enforce
History

Fri, 28 Aug 2026 22:15:00 +0000

Type Values Removed Values Added
First Time appeared Yamcs
Yamcs yamcs
Vendors & Products Yamcs
Yamcs yamcs

Fri, 28 Aug 2026 19:45:00 +0000

Type Values Removed Values Added
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.
Title Yamcs: WebSocket subscription handlers omit the privilege checks their REST siblings enforce
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-28T17:09:53.114Z

Reserved: 2026-06-16T23:01:04.075Z

Link: CVE-2026-55545

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-28T20:18:28.380

Modified: 2026-08-28T20:18:28.380

Link: CVE-2026-55545

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-28T22:00:14Z

Weaknesses