CVE-2026-46562

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0% (61st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

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 computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
61st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 27, 2026

Last Modified

July 20, 2026

Advisory Details (5)

Auto-updated Oct 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 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
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

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 rangeFix by version rangeDependents
org.yamcs:yamcs-core0.29.3 ... 5.9.9 (165 versions)
  • every version up to 5.12.7: fixed in 5.12.7
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 118 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 18 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46562?
CVE-2026-46562 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-46562 published?
The CVE record for CVE-2026-46562 was published on May 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 20, 2026; the record at its source may have been updated since.
Is CVE-2026-46562 actively exploited?
CVE-2026-46562 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46562?
CVE-2026-46562 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46562?
A fix for CVE-2026-46562 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46562 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs