CVE-2026-16438

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (12th 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
Trending — 3 sources updated this week
9.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.4Exploit: None knownExposed services: Not assessed

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

Incorrect Privilege Assignment vulnerability in Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, ICONICS Suite versions 10.97.3 and prior, Hyper Historian versions 10.97.3 and prior, AnalytiX versions 10.97.3 and prior, MobileHMI 10.97.3 and prior, MC Works64 all versions, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97.3 and prior, ICONICS Suite versions 10.97.3 and prior, Hyper Historian versions 10.97.3 and prior, AnalytiX versions 10.97.3 and prior, and MobileHMI 10.97.3 and prior allows an attacker who can log in using the same administrator account for the affected products to launch and operate DCOM objects locally or remotely. During installation, the installers of the affected products unnecessarily grant default DCOM permissions to the administrator account of the affected products. Users with that administrator accounts can locally or remotely launch and operate DCOM objects that should require UAC elevation. As a result, the attacker may disclose, tamper with, destroy, or delete internal information, or cause the affected system to enter a denial-of-service (DoS) condition.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (1)

Auto-updated Oct 15, 2026
No fix on record yet.
Web page
https://www.mitsubishielectric.com/psirt/vulnerability/pdf/2026-006_en.pdf

Vendor Advisories for CVE-2026-16438(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 32× 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.

  1. 2026-10-21 16:40 UTCEG score recompute
  2. 2026-10-21 16:40 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-20 17:40 UTCEG score recompute
  5. 2026-10-20 17:40 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  6. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-20 11:03 UTCEG score recompute
  8. 2026-10-20 11:02 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  9. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-19 12:02 UTCEG score recompute
  11. 2026-10-19 12:01 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  12. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-18 10:13 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  14. 2026-10-18 04:00 UTCEG score recompute
  15. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-10-17 05:27 UTCEG score recompute
  17. 2026-10-17 05:27 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  18. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-10-16 06:26 UTCEG score recompute
  20. 2026-10-16 06:26 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  21. 2026-10-16 05:47 UTCEG score recompute
  22. 2026-10-16 05:47 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  23. 2026-10-15 20:46 UTCEG score recompute
  24. 2026-10-15 20:46 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
Show 7 more
  1. 2026-10-15 15:27 UTCEG score recompute
  2. 2026-10-15 15:26 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  3. 2026-10-15 14:23 UTCEG score recompute
  4. 2026-10-15 14:23 UTCGHSA enrichmentGHSA-qcw9-8pcc-76g9 · GitHub severity CRITICAL
  5. 2026-10-15 09:27 UTCEG score recompute
  6. 2026-10-15 08:50 UTCEG score recomputeFirst assessed: 9.4 CRITICAL
  7. 2026-10-15 08:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16438?
CVE-2026-16438 is a critical-severity vulnerability; its CVE record was published on October 15, 2026. Incorrect Privilege Assignment vulnerability in Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, ICONICS Suite versions 10.97.3 and prior, Hyper Historian versions 10.97.3 and prior, AnalytiX versions 10.97.3 and prior, MobileHMI 10.97.3 and prior, MC Works64 all versions, Mitsubishi…
When was the CVE record for CVE-2026-16438 published?
The CVE record for CVE-2026-16438 was published on October 15, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-16438 actively exploited?
CVE-2026-16438 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16438?
CVE-2026-16438 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16438?
No fix for CVE-2026-16438 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-16438 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16438

Explore →

Is Your Infrastructure Affected by CVE-2026-16438?

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

Book a Demo →Browse All CVEs