Yamcs: No Rate Limiting on Authentication Endpoint
33Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 6.5epss 2.1%
from disclosure to weapon0 days
Published on NVDJul 16
1st PoCMay 29
exploitation probability
2.1%top 20% of all CVEs
observed exploitation
nono source reports it
2 public exploit(s)
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected products
yamcs · yamcspublic PoCs found — 2
exploitdbwww.exploit-db.com/exploits/52605unverifiedgithubgithub.com/ex-cal1bur/CVE-2026-44596★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83https://github.com/yamcs/yamcs/commit/64392df531fbcbc65f19ee5724c4c23d289f49fchttps://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.7https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.0https://github.com/yamcs/yamcs/security/advisories/GHSA-w5r6-mcgq-7pq4