CVE-2026-55521: Yamcs core Yamcs Core API Has Multiple Vulnerability
HIGHCVE-2026-55521 is a HIGH (CVSS 8.8) yamcs core api has multiple vulnerability (CWE-862: Missing Authorization) affecting Yamcs core libraries in the Maven ecosystem. The issue involves yamcs core api has multiple missing function level access control vulnerabilities. Remediation is available by upgrading affected packages to version 5.13.2, 5.12.8.
CVE-2026-55521 at a Glance
Security Impact
CVSS: 8.8
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:H/A:H).
How to Fix CVE-2026-55521
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.
<dependency>
<groupId>org.yamcs</groupId>
<artifactId>yamcs-core</artifactId>
<version>5.13.2</version>
</dependency>
<dependency>
<groupId>org.yamcs</groupId>
<artifactId>yamcs-core</artifactId>
<version>5.12.8</version>
</dependency>
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-55521, 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.13.2), 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
CVE-2026-55521 Affected Yamcs core Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.yamcs:yamcs-core
|
Maven |
≥ 5.13.0
< 5.13.2
|
5.13.2
|
|
org.yamcs:yamcs-core
|
Maven |
< 5.12.8
|
5.12.8
|
References
Frequently Asked Questions
What is CVE-2026-55521?
Which Yamcs core versions are affected?
What version fixes CVE-2026-55521?
Is yamcs-core affected?
What is the CVSS score of CVE-2026-55521?
What CWE is associated with CVE-2026-55521?
How can I check Maven dependencies for CVE-2026-55521?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-962x-ccwf-8x6p",
"modified" : "2026-08-28T17:09:35Z",
"published" : "2026-08-28T17:09:35Z",
"aliases" : [ "CVE-2026-55521" ],
"summary" : "Yamcs Core API has Multiple Missing Function Level Access Control vulnerabilities",
"details" : "### Summary\nMultiple Missing Function Level Access Control vulnerabilities exist in the Yamcs Core API. These vulnerabilities allow any authenticated user, regardless of their assigned roles or privileges (e.g., an unprivileged \"Guest\"), to bypass intended access controls. An attacker can exploit these flaws to extract sensitive telemetry metadata, disrupt satellite communication link protocols (COP-1), and manipulate the global simulation time, severely impacting the confidentiality, integrity, and availability of the system.\n\n### Details\nYamcs utilizes a robust Role-Based Access Control (RBAC) model with `SystemPrivilege` and `ObjectPrivilege` to restrict administrative actions and data retrieval. However, three critical API controllers completely omit these authorization checks before executing internal business logic:\n\n1. **`IndexesApi.java` (Information Disclosure):** Unlike `PacketsApi.java`, which filters results using `ctx.user.hasObjectPrivilege(ObjectPrivilegeType.ReadPacket, packetName)`, methods in `IndexesApi` (such as `listPacketIndex` and `listEventIndex`) directly retrieve and return archive records from the `CcsdsTmIndex` without verifying if the user has the required Object Privileges.\n2. **`Cop1Api.java` (Denial of Service / Integrity):** Modifying the COP-1 telecommand protocol state is an administrative action requiring `SystemPrivilege.ControlLinks`. However, endpoints in `Cop1Api` (e.g., `disable`, `resume`, `initialize`, `updateConfig`) process link state alterations without calling `ctx.checkSystemPrivilege(...)`.\n3. **`TimeApi.java` (Denial of Service / Integrity):** The `setTime` method allows modification of the global `SimulationTimeService` (affecting all processors, telemetry, and tests in that instance). This endpoint fails to assert any system privileges before applying the requested simulation speed or time jumps.\n\n### PoC\n**Prerequisite:** Obtain valid credentials for a completely unprivileged user (e.g., `user_without_priv:password` with no roles assigned).\n\n**PoC 1: Extracting Packet Indexes (`IndexesApi`)**\n```bash\ncurl -s -X GET \"http://localhost:8090/api/archive/simulator/packet-index\" \\\n -u \"user_without_priv:password\"\n```\n*Result:* Returns HTTP 200 OK with a full JSON array of packet indexes, bypassing Object Privilege checks and leaking system metadata.\n\n**PoC 2: Disabling COP-1 Protocol (`Cop1Api`)**\n```bash\ncurl -s -X POST \"http://localhost:8090/api/cop1/simulator/tc_sim:disable\" \\\n -u \"user_without_priv:password\" \\\n -H \"Content-Type: application/json\" -d '{}'\n```\n*Result:* The server processes the request past the authorization layer. Depending on the link configuration, it will either successfully disable COP-1 or return `400 BadRequestException` confirming the link does not support COP-1. The absence of a `403 Forbidden` confirms the authorization bypass.\n\n**PoC 3: Manipulating Simulation Time (`TimeApi`)**\n```bash\ncurl -s -X POST \"http://localhost:8090/api/instances/simulator:setTime\" \\\n -u \"user_without_priv:password\" \\\n -H \"Content-Type: application/json\" -d '{\"speed\": 10.0}'\n```\n*Result:* The server processes the request past the authorization layer. It changes the global simulation speed if the service is active, or returns `400 BadRequestException: Cannot set time for a non-simulation TimeService`. The absence of a `403 Forbidden` confirms the authorization bypass.\n\n### Impact\nThe vulnerability impacts instances of Yamcs exposing the REST API. \n* **Confidentiality:** Unprivileged users can enumerate all historical telemetry packet and event metadata.\n* **Integrity & Availability:** Attackers can disable critical satellite telecommand protocols (COP-1) causing command transmission failures. They can also manipulate the global simulation time, disrupting processors, automated tests, and all other users relying on the simulation environment.\n\n### PoC Images:\n- Check user permission\n<img width=\"1218\" height=\"951\" alt=\"image\" src=\"https://github.com/user-attachments/assets/fa7b1f1b-70fc-4796-805a-70acb84686d3\" />\n\n- Check admin permission and access API:\n<img width=\"1768\" height=\"555\" alt=\"image\" src=\"https://github.com/user-attachments/assets/844364f7-5e26-4c15-8809-6512f10ffbab\" />\n\n- Check user no permission - get response same with user admin:\n<img width=\"1264\" height=\"885\" alt=\"image\" src=\"https://github.com/user-attachments/assets/8773cef6-f940-48f7-a382-0eb87b8767d4\" />\n<img width=\"1243\" height=\"358\" alt=\"image\" src=\"https://github.com/user-attachments/assets/3288f092-7114-48d6-9e5c-9aeaf20d95d4\" />",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"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"
}
}, {
"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"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/yamcs/yamcs/security/advisories/GHSA-962x-ccwf-8x6p"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/yamcs/yamcs"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-862" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-28T17:09:35Z",
"nvd_published_at" : null
}
}