CVE-2026-46562

CRITICALPre-NVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 31% 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: 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, the Nashorn ScriptEngine used to evaluate user-supplied JavaScript algorithm text in yamcs-core/src/main/java/org/yamcs/algorithms/ScriptAlgorithmExecutorFactory.java was constructed without a ClassFilter, so a user with the ChangeMissionDatabase privilege could override an algorithm through the MdbOverrideApi.updateAlgorithm endpoint and supply JavaScript that reaches arbitrary Java classes (for example Java.type("java.lang.Runtime").getRuntime().exec(...)) to execute arbitrary OS commands as the Yamcs process; in the default configuration with no security.yaml the built-in guest user has superuser=true, making the issue reachable without authentication. This issue is fixed in versions 5.12.7 and 5.13.0, which disable algorithm editing by default.

CVSS v3
9.8
EG Score
9.8(low)
EPSS
68.9%
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

Remote Code Execution via Mission Database algorithm override · Advisory · yamcs/yamcs · GitHub

https://github.com/yamcs/yamcs/security/advisories/GHSA-vmwp-vh32-rj75

Vendor Advisories for CVE-2026-46562(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(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 38× 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 132 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46562?
CVE-2026-46562 is a critical vulnerability published on May 27, 2026. Yamcs is a mission control framework. Prior to 5.12.7, the Nashorn ScriptEngine used to evaluate user-supplied JavaScript algorithm text in yamcs-core/src/main/java/org/yamcs/algorithms/ScriptAlgorithmExecutorFactory.java was constructed without a ClassFilter, so a user with the…
When was CVE-2026-46562 disclosed?
CVE-2026-46562 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-46562 actively exploited?
CVE-2026-46562 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 68.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46562?
CVE-2026-46562 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-46562?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46562, 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-46562

Explore →

Is Your Infrastructure Affected by CVE-2026-46562?

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

Start Free Scan →Browse All CVEs