Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| yamcs | yamcs | < 5.12.7 | — |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
Exploit-DB 1
- YAMCS yamcs-core 5.12.7 - No Rate Limiting EDB-52605 · webapps · May 30, 2026
GitHub 1 repository
-
ex-cal1bur/CVE-2026-44596 ★ 0 · May 29, 2026
YAMCS yamcs-core < 5.12.7 lacks rate limiting on POST /auth/token. An unauthenticated attacker can perform unlimited brute-force attempts against any account. Never returns HTTP 429. Fixed in 5.12.7.
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Maven | org.yamcs:yamcs-core | < 5.12.7 | 5.12.7 | GHSA-w5r6-mcgq-7pq4 |
References
- https://github.com/yamcs/yamcs/security/advisories/GHSA-w5r6-mcgq-7pq4
- https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83
- https://github.com/yamcs/yamcs/commit/64392df531fbcbc65f19ee5724c4c23d289f49fc
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.7
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.0