CVE-2026-44596 yamcs vulnerability
Yamcs is a mission control framework. Prior to 5.12.7, the authentication endpoint POST /auth/token in yamcs-core, handled by yamcs-core/src/main/java/org/yamcs/http/auth/AuthHandler.java, lacked any rate limiting, account lockout, or failed-attempt throttling, so an unauthenticated remote attacker could perform unlimited password-guessing attempts against any user account, significantly increasing the risk of successful brute-force attacks. 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-44596 affects Yamcs before the fixed releases. The login endpoint did not slow or block repeated failed attempts, so attackers could try many passwords remotely. Upgrade Yamcs and add login protection.
- Upgrade Yamcs to 5.12.7, 5.13.0, or a newer fixed version for CVE-2026-44596.
- Add rate limiting, failed-login throttling, and alerting on the authentication endpoint.
- Require strong passwords and multi-factor authentication where possible.
- Review authentication logs for repeated failures against the same users.
- Reset passwords for accounts that show suspicious login activity.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the Yamcs version is 5.12.7, 5.13.0, or newer.
- Test repeated failed logins in staging and confirm they are slowed, blocked, or alerted.
- Check logs for brute-force activity during the exposure window.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-44596?
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.