CVE-2026-55545: Yamcs core Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-fwww-cp23-7f5g
CVSS 6.5
CWE-862
Published
Advisory Summary

CVE-2026-55545 is a MODERATE (CVSS 6.5) remote code execution vulnerability (CWE-862: Missing Authorization) affecting Yamcs core libraries in the Maven ecosystem. The issue involves yamcs's websocket subscription handlers omit the privilege checks their rest siblings enforce. Remediation is available by upgrading affected packages to version 5.12.8, 5.13.2.

CVE-2026-55545 at a Glance

CVE Identifier CVE-2026-55545
GHSA Identifier GHSA-fwww-cp23-7f5g
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-862: Missing Authorization
Affected Product Yamcs core
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-55545

To remediate this vulnerability, upgrade all affected Yamcs core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.yamcs:yamcs-core fixed: 5.12.8
<dependency>
    <groupId>org.yamcs</groupId>
    <artifactId>yamcs-core</artifactId>
    <version>5.12.8</version>
</dependency>
org.yamcs:yamcs-core fixed: 5.13.2
<dependency>
    <groupId>org.yamcs</groupId>
    <artifactId>yamcs-core</artifactId>
    <version>5.13.2</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.yamcs

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-55545, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.yamcs

Analyze the terminal output to locate any version of Yamcs core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.12.8), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.yamcs command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In Yamcs core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**Asset / scope:** Yamcs 5.12.7 WebSocket topics (`packets`, `algorithm-status`, `mdb-changes`) ## Summary Several WebSocket subscription handlers do not perform the privilege check that their REST counterparts enforce, so a principal subscribing over WebSocket receives data the REST API would have scoped or denied. ## Root cause - `packets` (`PacketsApi.subscribePackets`) performs no `ReadPacket` check, while the REST siblings do (`listPackets:128`, `streamPackets:256`, `subscribeContainers:538`). A principal with a narrow `ReadPacket` scope receives the raw binary of all TM packets on the processor. - `algorithm-status` (`ProcessingApi.subscribeAlgorithmStatus`) performs no check, while REST `getAlgorithmStatus` enforces `checkObjectPrivileges(ReadAlgorithm, ...)` (`:467`). - `mdb-changes` (`MdbOverrideApi.subscribeMdbChanges`) performs no check, while base MDB reads require `GetMissionDatabase`. ## Remediation Bring each WebSocket subscription handler to parity with its REST sibling's privilege check (`ReadPacket`, `ReadAlgorithm`, `GetMissionDatabase`). This is the same declarative fail-closed fix as Report 1. ## Supporting material Subsystem source audit of the WS-vs-REST authorization parity. Available on request. -- ## Disclosure and credit This was found by Cipher / Causal Security - https://causalsecurity.com/. We are coordinating disclosure via this report and request CVEs where you agree they qualify. We propose the 90-day window stated in your security policy. We might publish a write-up after a fix and the agreed window.

CVE-2026-55545 Affected Yamcs core Versions

2 component(s)
Fixed Versions:
5.12.85.13.2
Product / Package Ecosystem Affected Versions Fixed Version
org.yamcs:yamcs-core
Maven
< 5.12.8
5.12.8
org.yamcs:yamcs-core
Maven
≥ 5.13.0
< 5.13.2
5.13.2

References

Frequently Asked Questions

What is CVE-2026-55545?
CVE-2026-55545 is a security vulnerability in Yamcs core involving Yamcs's WebSocket subscription handlers omit the privilege checks their REST siblings enforce under CWE-862: Missing Authorization.
Which Yamcs core versions are affected?
Affected versions include releases prior to 5.12.8, 5.13.2 across affected packages: org.yamcs:yamcs-core.
What version fixes CVE-2026-55545?
Upgrading to 5.12.8, 5.13.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is yamcs-core affected?
Yes, org.yamcs:yamcs-core is affected in releases prior to 5.12.8, 5.13.2. Upgrade your dependency to 5.12.8, 5.13.2 or later.
What is the CVSS score of CVE-2026-55545?
CVE-2026-55545 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-55545?
CVE-2026-55545 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Maven dependencies for CVE-2026-55545?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.yamcs'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fwww-cp23-7f5g",
  "modified" : "2026-08-28T17:10:26Z",
  "published" : "2026-08-28T17:10:26Z",
  "aliases" : [ "CVE-2026-55545" ],
  "summary" : "Yamcs's WebSocket subscription handlers omit the privilege checks their REST siblings enforce",
  "details" : "**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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.yamcs:yamcs-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.12.8"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.12.7"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.yamcs:yamcs-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.13.0"
      }, {
        "fixed" : "5.13.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.13.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/yamcs/yamcs/security/advisories/GHSA-fwww-cp23-7f5g"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/yamcs/yamcs/commit/0691731846c5a0aca81b88fabbd2cd51d56fe076"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/yamcs/yamcs/commit/12864af555e6ca4941b01c1f1217859cc0492ce0"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/yamcs/yamcs"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-28T17:10:26Z",
    "nvd_published_at" : null
  }
}