CVE-2026-44632

CRITICALPre-NVD 9.19.1
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 35% 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: cna:github_m, epss
Elevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(low)
EPSS
65.3%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 16, 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.0
github_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.7
github_commit

commit 4ff8fda642ea (yamcs/yamcs)

Fix landed in yamcs/yamcs commit 4ff8fda642ea — awaiting tagged release

https://github.com/yamcs/yamcs/commit/4ff8fda642ea8c3309a4d3f379aa77b763148992
github_commit

commit 3c550348f866 (yamcs/yamcs)

Fix landed in yamcs/yamcs commit 3c550348f866 — awaiting tagged release

https://github.com/yamcs/yamcs/commit/3c550348f866af4675d2ba4a51d8d12b7c7c6011
github 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-9wm6

Vendor 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)
PackageVulnerable rangeFixed inDependents
org.yamcs:yamcs-core0.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 0× in last 7d / 27× 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.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-07-01 17:01 UTCEG score recompute
  2. 2026-07-01 11:53 UTCEG score recompute
  3. 2026-06-29 19:52 UTCEG score recompute
  4. 2026-06-29 14:45 UTCEG score recompute
  5. 2026-06-29 02:46 UTCEG score recompute
  6. 2026-06-28 22:26 UTCEG score recompute
  7. 2026-06-28 13:56 UTCEG score recompute
  8. 2026-06-28 09:27 UTCEG score recompute
  9. 2026-06-28 05:07 UTCEG score recompute
  10. 2026-06-28 00:47 UTCEG score recompute
  11. 2026-06-27 20:04 UTCEG score recompute
  12. 2026-06-27 15:42 UTCEG score recompute
  13. 2026-06-27 11:19 UTCEG score recompute
  14. 2026-06-27 06:57 UTCEG score recompute
  15. 2026-06-26 21:49 UTCEG score recompute
  16. 2026-06-26 17:27 UTCEG score recompute
  17. 2026-06-26 03:24 UTCEG score recompute
  18. 2026-06-25 23:03 UTCEG score recompute
  19. 2026-06-25 18:19 UTCEG score recompute
  20. 2026-06-25 13:57 UTCEG score recompute
  21. 2026-06-25 09:36 UTCEG score recompute
  22. 2026-06-18 03:58 UTCEG score recompute
  23. 2026-06-17 23:37 UTCEG score recompute
  24. 2026-06-17 19:08 UTCEG score recompute
  25. 2026-06-17 14:16 UTCEG score recompute
Show 75 more
  1. 2026-06-17 09:56 UTCEG score recompute
  2. 2026-06-17 05:34 UTCEG score recompute
  3. 2026-06-17 01:13 UTCEG score recompute
  4. 2026-06-16 20:53 UTCEG score recompute
  5. 2026-06-16 16:33 UTCEG score recompute
  6. 2026-06-16 11:27 UTCEG score recompute
  7. 2026-06-16 07:06 UTCEG score recompute
  8. 2026-06-16 02:47 UTCEG score recompute
  9. 2026-06-15 22:27 UTCEG score recompute
  10. 2026-06-15 13:40 UTCEG score recompute
  11. 2026-06-15 08:02 UTCEG score recompute
  12. 2026-06-15 03:39 UTCEG score recompute
  13. 2026-06-14 23:19 UTCEG score recompute
  14. 2026-06-14 23:18 UTCEPSS rescore
  15. 2026-06-14 18:58 UTCEG score recompute
  16. 2026-06-14 14:39 UTCEG score recompute
  17. 2026-06-14 10:18 UTCEG score recompute
  18. 2026-06-14 05:57 UTCEG score recompute
  19. 2026-06-14 01:24 UTCEG score recompute
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-13 21:02 UTCEG score recompute
  22. 2026-06-13 12:02 UTCEG score recompute
  23. 2026-06-13 07:42 UTCEG score recompute
  24. 2026-06-13 03:20 UTCEG score recompute
  25. 2026-06-12 23:12 UTCEPSS rescore
  26. 2026-06-12 22:58 UTCEG score recompute
  27. 2026-06-12 18:38 UTCEG score recompute
  28. 2026-06-12 14:17 UTCEG score recompute
  29. 2026-06-12 09:58 UTCEG score recompute
  30. 2026-06-12 05:36 UTCEG score recompute
  31. 2026-06-12 01:16 UTCEG score recompute
  32. 2026-06-11 20:56 UTCEG score recompute
  33. 2026-06-11 16:36 UTCEG score recompute
  34. 2026-06-11 12:11 UTCEG score recompute
  35. 2026-06-11 07:50 UTCEG score recompute
  36. 2026-06-11 03:31 UTCEG score recompute
  37. 2026-06-10 23:10 UTCEG score recompute
  38. 2026-06-10 18:51 UTCEG score recompute
  39. 2026-06-10 14:31 UTCEG score recompute
  40. 2026-06-10 10:11 UTCEG score recompute
  41. 2026-06-10 05:51 UTCEG score recompute
  42. 2026-06-10 01:31 UTCEG score recompute
  43. 2026-06-09 21:11 UTCEG score recompute
  44. 2026-06-09 16:45 UTCEG score recompute
  45. 2026-06-09 12:25 UTCEG score recompute
  46. 2026-06-09 08:04 UTCEG score recompute
  47. 2026-06-09 03:44 UTCEG score recompute
  48. 2026-06-08 23:23 UTCEG score recompute
  49. 2026-06-08 19:02 UTCEG score recompute
  50. 2026-06-08 11:47 UTCEG score recompute
  51. 2026-06-08 07:27 UTCEG score recompute
  52. 2026-06-08 03:07 UTCEG score recompute
  53. 2026-06-07 22:47 UTCEG score recompute
  54. 2026-06-07 18:27 UTCEG score recompute
  55. 2026-06-07 14:07 UTCEG score recompute
  56. 2026-06-07 09:41 UTCEG score recompute
  57. 2026-06-07 05:21 UTCEG score recompute
  58. 2026-06-07 01:00 UTCEG score recompute
  59. 2026-06-06 20:40 UTCEG score recompute
  60. 2026-06-06 16:20 UTCEG score recompute
  61. 2026-06-06 12:00 UTCEG score recompute
  62. 2026-06-06 07:40 UTCEG score recompute
  63. 2026-06-06 03:20 UTCEG score recompute
  64. 2026-06-05 22:59 UTCEG score recompute
  65. 2026-06-05 18:39 UTCEG score recompute
  66. 2026-06-05 14:19 UTCEG score recompute
  67. 2026-06-05 09:59 UTCEG score recompute
  68. 2026-06-05 05:39 UTCEG score recompute
  69. 2026-06-05 01:19 UTCEG score recompute
  70. 2026-06-04 20:59 UTCEG score recompute
  71. 2026-06-04 16:39 UTCEG score recompute
  72. 2026-06-04 12:19 UTCEG score recompute
  73. 2026-06-04 07:59 UTCEG score recompute
  74. 2026-06-04 03:39 UTCEG score recompute
  75. 2026-06-03 23:19 UTCEG score recompute

Related CVEs(same CWE)

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 16, 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 65.3% 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). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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

Explore →

Is Your Infrastructure Affected by CVE-2026-44632?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs