RCE in openPDC/openHistorian — widely used OT/utility grid software; exploit can lead to system takeover and operational disruption; CISA published advisory.
CVE-2026-100730
Deserialization RCE in openPDC/openHistorian service console
Is CVE-2026-100730 being exploited?
Not confirmed. CVE-2026-100730 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.
How severe is CVE-2026-100730?
CVE-2026-100730 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-100730?
Not known from our data. No patch reference has been recorded for CVE-2026-100730, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-100730 affect?
CVE-2026-100730 affects openPDC, openHistorian, service console interface. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-100730?
Isolate and block access to the service console, enable Windows Authentication, apply vendor mitigations/patches when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Deserialization leads to remote code execution as the service account; unauthenticated network attackers can reach it if Windows Authentication is not enabled.
Immediate action required
- affected< 2.8.580
- affected< 2.8.585
- affected< 2.9.477
- affected< 2.9.482
- affected< 2.9.477
- affected< 2.9.482
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.