CVE Intelligence
Critical Insecure deserialization

CVE-2026-100730 — Grid Protection Alliance openPDC and openHistorian Deserialization of Untrusted Data

A service console interface on openPDC and openHistorian deserializes a client-supplied data structure. On systems using Windows Authentication, an attacker must already be authenticated to reach this function; on systems without Windows Authentication, this is reachable by an unauthenticated network attacker. This allows an attacker to trigger deserialization of an arbitrary object graph, which could allow remote code execution under the privileges of the affected service account.

Published Oct 9, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: icscert

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.6% (30-day exploitation probability)+7
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.63%
ahead of 49% of scored CVEs · Oct 14, 2026
Affects
Grid Protection Alliance
openHistorian and 2 more
CVSS base
9.8
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Grid Protection Alliance openHistorian, Grid Protection Alliance openPDC, Grid Protection Alliance openPDC (Docker image)).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Grid Protection Alliance openHistorian < 2.8.580< 2.8.585 Vulnerable CVE Program (cve.org) e CISA ADP
Grid Protection Alliance openPDC < 2.9.477< 2.9.482 Vulnerable CVE Program (cve.org) e CISA ADP
Grid Protection Alliance openPDC (Docker image) < 2.9.477< 2.9.482 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.3 CVSS 4.0 Critical — — ics-cert@hq.dhs.gov via NIST National Vulnerability Database
9.3 CVSS 4.0 Critical — — icscert via CVE Program (cve.org) e CISA ADP
9.8 CVSS 3.1 Critical 3.9 5.9 ics-cert@hq.dhs.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.8 CVSS 3.1 Critical — — icscert via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: ics-cert@hq.dhs.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-502 · Deserialization of Untrusted Data

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.63%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor serialized objects in requests and unexpected processes spawned by the runtime.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)application logs

Analysis and videos

CVE-2026-100730: Grid Protection Alliance openPDC and openHistorian Deserialization of Untrusted Data
CVE-2026-100730 is a critical deserialization of untrusted data flaw (CWE-502) in a service console interface of Grid Protection Alliance openPDC and openHistorian. The record reports CVSS 3.1 9.8 and CVSS 4.0 9.3, and it describes possible remote code execution under the service account privileges. The sources consulted do not show confirmed exploitation, and the record lists no fixed versions, so operators should check the vendor and CISA guidance.

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · grid protection alliance/openpdc, grid protection alliance/openpdc (docker image), grid protection alliance/openhistoria
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 9, 2026 · icscert

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Grid Protection Alliance
every CVE for this vendor
Insecure deserialization
same class
CWE-502
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-105278 Grid Protection Alliance openPDC (Docker image) Use of Hard-coded Credentials 6d
  • CVE-2026-85479 Grid Protection Alliance openPDC and openHistorian Missing Authentication for Critical Function 6d
  • CVE-2026-104629 Grid Protection Alliance openPDC and openHistorian Use of Externally-Controlled Input to Select Classes or Code 6d
  • CVE-2026-105281 Grid Protection Alliance openPDC and openHistorian Missing Authentication for Critical Function 6d
  • CVE-2026-101022 Grid Protection Alliance openPDC and openHistorian Server-Side Request Forgery (SSRF) 6d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-100730 is "Grid Protection Alliance openPDC and openHistorian Deserialization of Untrusted Data", rated Critical. It affects openHistorian (Grid Protection Alliance); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 0.63% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.