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.
CVE-2026-44596
CRITICALNVD 9.89.8—Trending — 4 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.8%, top 24% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 75.8%
- KEV
- Not listed
Published
May 27, 2026
Last Modified
July 17, 2026
Advisory Details (5)
Auto-updated Jul 17, 2026🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github Patch Available🟡 PoC Available
No Rate Limiting on Authentication Endpoint · Advisory · yamcs/yamcs · GitHub
https://github.com/yamcs/yamcs/security/advisories/GHSA-w5r6-mcgq-7pq4github_release Patch Available
Yamcs 5.13.0
Patch available: yamcs/yamcs yamcs-5.13.0
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.0github_release Patch Available
Yamcs 5.12.7
Patch available: yamcs/yamcs yamcs-5.12.7
https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.7github_commit
commit 64392df531fb (yamcs/yamcs)
Fix landed in yamcs/yamcs commit 64392df531fb — awaiting tagged release
https://github.com/yamcs/yamcs/commit/64392df531fbcbc65f19ee5724c4c23d289f49fcgithub_commit
commit 309218c65168 (yamcs/yamcs)
Fix landed in yamcs/yamcs commit 309218c65168 — awaiting tagged release
https://github.com/yamcs/yamcs/commit/309218c651680f79df11a8d0f8628f7033f98a83Vendor Advisories for CVE-2026-44596(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.yamcs:yamcs-core | 0.29.3 ... 5.9.9 (165 versions) | 5.12.7 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:15 UTCEG score recompute▲ 3.30
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 05:52 UTCOSV refresh
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 20:00 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-27 00:14 UTCEG score recompute
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-52605First seen May 30, 2026
YAMCS yamcs-core 5.12.7 - No Rate Limiting
Open source ↗
Related CVEs(same CWE)
Same CWE
10 shownCWE-307
Frequently asked(5)
What is CVE-2026-44596?
CVE-2026-44596 is a critical vulnerability published on May 27, 2026. 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…
When was CVE-2026-44596 disclosed?
CVE-2026-44596 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44596 actively exploited?
CVE-2026-44596 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 75.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44596?
CVE-2026-44596 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-44596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44596, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44596
Is Your Infrastructure Affected by CVE-2026-44596?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.