CVE-2026-44595 yamcs vulnerability
Yamcs is a mission control framework. Prior to 5.12.7, the IAM API endpoints listUsers, getUser, listGroups, and getGroup in yamcs-core did not enforce the required SystemPrivilege.ControlAccess check in yamcs-core/src/main/java/org/yamcs/http/api/IamApi.java, so any authenticated user, even one with low or no privileges, could enumerate all user accounts in the system including their usernames, superuser status, and group memberships. This issue is fixed in versions 5.12.7 and 5.13.0.
Browse Java security risksQuick answer
spaceapplications yamcs should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-44595 affects Yamcs before the fixed releases. Low-privilege users could list user and group details. Upgrade Yamcs and review who can access IAM APIs.
- Upgrade Yamcs to 5.12.7, 5.13.0, or a newer fixed version for CVE-2026-44595.
- Review Yamcs users and remove access that is no longer needed.
- Restrict IAM API access to trusted administrators only.
- Check logs for calls to listUsers, getUser, listGroups, and getGroup by low-privilege users.
- Treat exposed account and group data as sensitive and watch for follow-up phishing or login attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the Yamcs version includes the IAM privilege check fix.
- Test with a low-privilege account and confirm IAM user and group APIs are denied.
- Review audit logs for unexpected enumeration activity.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-44595?
spaceapplications yamcs should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.