Yamcs up to 5.12.7/5.13.1 IAM API IamApi.java privileges management

Summaryinfo

A vulnerability marked as critical has been reported in Yamcs up to 5.12.7/5.13.1. Affected by this vulnerability is the function IamApi.listRoles/IamApi.getRole/IamApi.listPrivileges of the file yamcs-core/src/main/java/org/yamcs/http/api/IamApi.java of the component IAM API. The manipulation leads to privileges management. This vulnerability is traded as CVE-2026-55547. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Yamcs up to 5.12.7/5.13.1 and classified as critical. This issue affects the function IamApi.listRoles/IamApi.getRole/IamApi.listPrivileges of the file yamcs-core/src/main/java/org/yamcs/http/api/IamApi.java of the component IAM API. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs omits SystemPrivilege.ControlAccess checks from IamApi.listRoles, IamApi.getRole, and IamApi.listPrivileges in yamcs-core/src/main/java/org/yamcs/http/api/IamApi.java. Any authenticated account can call GET /api/roles, GET /api/roles/{name}, and GET /api/privileges to enumerate available system privileges and configured role mappings. The disclosure reveals security configuration that can support targeted privilege-escalation attempts. This issue is fixed in versions 5.12.8 and 5.13.2.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-55547 since 06/17/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 5.12.8 or 5.13.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Yamcs

Version

• 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.13.0
• 5.13.1

Website

• Product: https://github.com/yamcs/yamcs/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion