Security configuration disclosure via missing IAM authorization
Published Aug 28, 2026 · Updated Aug 28, 2026
Missing authorization in Yamcs before 5.12.8 and 5.13.0 through 5.13.1 allows remote authenticated users to read IAM security metadata. IamApi.listRoles, IamApi.getRole, and IamApi.listPrivileges return role mappings and system privileges without checking ControlAccess. Any authenticated account can reach the endpoints, exposing configuration that supports targeted privilege-escalation attempts.
Summary
What happened
Missing authorization in Yamcs before 5.12.8 and 5.13.0 through 5.13.1 allows remote authenticated users to read IAM security metadata. IamApi.listRoles, IamApi.getRole, and IamApi.listPrivileges return role mappings and system privileges without checking ControlAccess. Any authenticated account can reach the endpoints, exposing configuration that supports targeted privilege-escalation attempts.
The record
- CVE
- CVE-2026-55547
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Space Applications Services
- Product
- Yamcs
- Classifications
- CWE-862, CWE-285, T1069
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.12.8
- Affected versionversion=>= 5.13.0, < 5.13.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream authenticated IAM enumeration proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo