Safeguard
Vulnerability Analysis•

openPDC and openHistorian: six CVEs in grid monitoring software

CISA's 8 October 2026 advisory ICSA-26-281-02 lists six flaws in Grid Protection Alliance openPDC and openHistorian, including a critical deserialization bug. No exploitation is reported.

Safeguard Security Team
3 min read

On 8 October 2026, CISA published ICSA-26-281-02 for Grid Protection Alliance openPDC and openHistorian, software used in the energy sector for phasor and time series data. CISA states that no known public exploitation specifically targeting these vulnerabilities has been reported to it. The researcher credited is Shubham Raj of Causal Security.

What's affected

openPDC before 2.9.482 and openHistorian before 2.8.585 are affected, with some CVEs fixed earlier at 2.9.477 and 2.8.580. The openPDC Docker image is affected and no fix is planned. GPA does not recommend production use of its published Docker images.

CVEWeaknessCVSS 3.1
CVE-2026-100730CWE-502 deserialization of untrusted data9.8
CVE-2026-105278Hard-coded credentials in the Docker image9.8
CVE-2026-104629Unsafe reflection8.8
CVE-2026-105281Missing authentication on the data publisher7.5
CVE-2026-85479Missing authentication on the STTP publisher5.3
CVE-2026-101022Server-side request forgery in Modbus connections4.3

The deserialization flaw can be reached without authentication on systems that do not use Windows Authentication. The default bindings were changed to loopback only for new installations. Upgraded systems keep old settings, so check them by hand.

What to do now

  1. Upgrade openPDC to 2.9.482 or later and openHistorian to 2.8.585 or later.
  2. Check which interfaces the data publishers listen on, and bind them to loopback unless remote access is required.
  3. Turn on Windows Authentication for the service console.
  4. Do not run the published Docker images in production. If you already do, change the administrative credential and restrict the management interface.
  5. Restrict Modbus destinations at the firewall and block loopback and RFC 1918 targets unless needed.
  6. Keep these systems off the internet and behind firewalls, as CISA advises.

How this could have been avoided

  • Authentication by default. Two of the six flaws are publishers that accept unauthenticated connections out of the box.
  • No fixed credentials in images. A forced password change at first start closes the Docker issue.
  • Safe config on upgrade. Applying the new loopback default to existing installs would protect upgraded systems.

Quick check

Why are upgraded openPDC systems possibly still exposed?

The loopback default applies only to new installations, so upgraded systems keep their previous listening settings until an operator changes them.

Sources

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.