Yamcs is a mission control framework. Prior to 5.12.7, a server-side code injection vulnerability existed in the Yamcs algorithm evaluation engine org.yamcs.algorithms.JavaExprAlgorithmExecutionFactory, which dynamically compiled and evaluated user-controlled algorithm text through the Janino compiler without enforcing a secure sandbox, so an authenticated user with the ChangeMissionDatabase privilege could override an existing algorithm's text via the mission database REST API and inject Java code (for example using java.lang.Runtime) to achieve remote code execution on the underlying host operating system. This issue is fixed in versions 5.12.7 and 5.13.0, which disable algorithm editing by default.
CVE-2026-44632
CRITICALPre-NVD 9.19.1—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 43% 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, secondary
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 57(Track*)EG Risk 57/100SSVC: Track*
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 computedSeverity91% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS
- 57.2%
- KEV
- Not listed
Published
May 27, 2026
Last Modified
July 17, 2026
Advisory Details (5)
Auto-updated Jul 16, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_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 4ff8fda642ea (yamcs/yamcs)
Fix landed in yamcs/yamcs commit 4ff8fda642ea — awaiting tagged release
https://github.com/yamcs/yamcs/commit/4ff8fda642ea8c3309a4d3f379aa77b763148992github_commit
commit 3c550348f866 (yamcs/yamcs)
Fix landed in yamcs/yamcs commit 3c550348f866 — awaiting tagged release
https://github.com/yamcs/yamcs/commit/3c550348f866af4675d2ba4a51d8d12b7c7c6011github Patch Available🟡 PoC Available
Server-Side Code Injection (RCE) via Janino Expression Engine in `JavaExprAlgorithmExecutionFactory` · Advisory · yamcs/yamcs · GitHub
https://github.com/yamcs/yamcs/security/advisories/GHSA-524g-x36v-9wm6Vendor Advisories for CVE-2026-44632(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 8× in last 7d / 8× 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
- 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 10:22 UTCOSV refresh
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 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
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
Frequently asked(5)
What is CVE-2026-44632?
CVE-2026-44632 is a critical vulnerability published on May 27, 2026. Yamcs is a mission control framework. Prior to 5.12.7, a server-side code injection vulnerability existed in the Yamcs algorithm evaluation engine org.yamcs.algorithms.JavaExprAlgorithmExecutionFactory, which dynamically compiled and evaluated user-controlled algorithm text through the Janino…
When was CVE-2026-44632 disclosed?
CVE-2026-44632 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-44632 actively exploited?
CVE-2026-44632 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44632?
CVE-2026-44632 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-44632?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44632, 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-44632
Is Your Infrastructure Affected by CVE-2026-44632?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.