Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach openPDC data publisher port
-
ExploitConnect without authentication
-
ExecutionSubscribe to internal publisher
-
ImpactEnumerate full device/measurement topology
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the openPDC internal data publisher interface, which in its DEFAULT configuration accepts connections without any authentication - no credentials, tokens, or user interaction are needed. The concrete prerequisite is simply that an attacker can establish a TCP connection to this publisher endpoint and issue a subscription request. The primary limiting factor is network exposure: in properly segmented OT/ICS environments the publisher is not reachable from untrusted networks, which sharply reduces realistic exposure, whereas flat networks or inadvertently exposed instances are fully exploitable. Impact is further bounded to read-only disclosure of device and measurement topology (VC:H, no integrity or availability impact), so the attacker cannot alter or disrupt operation through this flaw alone. |
| Impact | All signals point to a genuine but bounded confidentiality risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms remote, low-complexity, unauthenticated exploitation requiring no user interaction, which aligns cleanly with CWE-306 (Missing Authentication) and the description of an internal data publisher that accepts connections without authentication in its default configuration. However, impact is limited to VC:H with VI:N/VA:N - this is pure information disclosure of device and measurement topology, not code execution, data tampering, or denial of service, which is why the score lands at 8.7 rather than near 10. No EPSS score, KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the 8.7 reflects ease and reach of the disclosure, not weaponized impact. The practical risk is best understood as reconnaissance-grade: an attacker gains a full map of grid synchrophasor devices and measurements that could seed a follow-on OT attack, but exploitation presupposes network reachability to the publisher interface, which in well-segmented ICS environments is a meaningful limiter. Treat as a real priority for internet- or flat-network-exposed openPDC instances, and as lower urgency where OT segmentation isolates the interface. |
| Exploit ScenarioDerived | An attacker with network reachability to an openPDC host connects directly to the internal data publisher interface, which in its default configuration requires no authentication. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, the attacker simply subscribes and retrieves the complete device and measurement topology without credentials or user interaction. No public exploit is identified at time of analysis, but the interaction is trivial enough to script against any reachable instance. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 09, 2026
Unauthenticated access to the openPDC internal data publisher lets any host that can reach the service connect and subscribe without credentials, tokens, or user interaction, retrieving the complete device and measurement topology - the full model of phasor measurement units, devices, and signal names that describes a synchrophasor deployment. The affected software set, per vendor CPE entries, covers openPDC, the openPDC Docker image, and openHistorian, with CISA ICS advisory ICSA-26-281-02 documenting the missing-authentication weakness (CWE-306); the assessed vector requires no authentication (PR:N) and yields a high-confidentiality, read-only exposure with no integrity or availability impact, so an attacker cannot alter or disrupt operations through this flaw alone. No public exploit identified at time of analysis, and realistic risk is dominated by network exposure: properly segmented OT/ICS networks sharply limit reachability, while flat networks or inadvertently internet-exposed publisher endpoints are fully exploitable.
Earlier versions of this analysis (1)
Unauthenticated access to openPDC's internal data publisher lets a remote attacker pull the complete device and measurement topology of a deployment, an information-disclosure flaw rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) that leaks grid monitoring layout rather than allowing control or code execution. Affected per the supplied CPE data are openPDC, the openPDC Docker image, and openHistorian, all with unconstrained version ranges, so no fixed-version boundary is identifiable from the data; exposure exists specifically in the default configuration where the publisher accepts connections without credentials. No public exploit code and no confirmed active exploitation are associated with this CVE at time of analysis; the practical determinant of risk is whether the publisher port is reachable from an untrusted network segment.
RemediationAI
No vendor-released patch or exact fixed version is identified in the available advisory data at the time of analysis, so remediation should be driven by the guidance in CISA ICS advisory ICSA-26-281-02 (https://www.cisa.gov/news-events/ics-advisories/icsa-26-281-02, CSAF mirror at https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-281-02.json); check with Grid Protection Alliance for updated openPDC/openHistorian builds and apply them as soon as they are published. Until a fix is confirmed, the highest-value compensating control is to eliminate reachability to the internal data publisher from untrusted networks: enforce OT network segmentation so only known internal subscribers can open a TCP connection to the publisher endpoint, and add host or perimeter firewall rules allowing that port solely from the specific source addresses that legitimately consume the data - the trade-off is that mis-scoped rules break dependent internal applications, so the allow-list must be validated against actual subscriber traffic before enforcement. If the internal data publisher is not required on a given node, disable the service entirely (its cost is the loss of internal real-time telemetry to local consumers), and where it must remain enabled, bind it to loopback or a dedicated management interface rather than all interfaces, accepting that remote consumers will need to be relocated or proxied. Finally, monitor for anomalous subscription requests to this interface as detection for exploitation attempts, since any successful connection in the default configuration is, by definition, unauthenticated and should be treated as suspicious unless it originates from a known internal subscriber.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
openPDC is the Grid Protection Alliance's open-source phasor data concentrator, a Windows/.NET time-series application used in electric-grid synchrophasor deployments to aggregate IEEE C37.118 phasor measurement data and to serve that data to downstream consumers; openHistorian is the companion time-series archive, and both are distributed as native builds and Docker images (CPE entries cpe:2.3:a:grid_protection_alliance:openpdc:*, cpe:2.3:a:grid_protection_alliance:openpdc_(docker_image):*, and cpe:2.3:a:grid_protection_alliance:openhistorian:*). The vulnerable component is the internal data publisher, a TCP listener that internal applications use to subscribe to real-time measurements and topology metadata. The root cause is CWE-306 (Missing Authentication for Critical Function): in its default configuration the publisher accepts connections and processes subscription requests without validating any credential, so the enumeration of devices and measurement points is a pure architectural oversight rather than an injection or memory-safety defect. Because the exposure is limited to reading the published data model, the assessed impact is confidentiality-only (VC:H with VI:N/VA:N and no subsequent-system impact), which is why the CISA-assigned severity is high but not critical despite the unauthenticated network attack vector.
Know when Openpdc gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Remote unauthenticated connection to a default-open publisher (AV:N/AC:L/PR:N/UI:N) yielding full topology disclosure (C:H) with no write or availability impact (I:N/A:N).
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
Lifecycle Timeline
3DescriptionCVE.org
The internal data publisher on openPDC accepts network connections without authentication in its default configuration. An unauthenticated network attacker can connect to this interface and retrieve the complete device and measurement topology of the system.
Executive ViewAI
openPDC, the openPDC Docker image, and openHistorian expose an internal data publisher that can be accessed without authentication, allowing any reachable host to retrieve the full synchrophasor device and measurement topology. For utilities and grid operators, this creates a reconnaissance risk that could support follow-on attacks against OT/ICS environments, particularly where these systems are internet-facing or reside on flat networks. No vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, so leadership should prioritize exposure reduction and interim access controls.
No vendor-released patch identified at time of analysis. Restrict network access to the openPDC/openHistorian internal data publisher using firewall rules, ACLs, network segmentation, and OT DMZ isolation; disable the publisher if not required; require VPN or authenticated jump host; monitor for unauthorized subscription activity; follow CISA ICS advisory ICSA-26-281-02 for updated mitigations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Insecure deserialization in the service console interface of openPDC and openHistorian lets an attacker submit a crafted
Unauthenticated access to the STTP-based data publisher in Grid Protection Alliance openPDC, the openPDC Docker image, a
Arbitrary constructor code execution in Grid Protection Alliance openPDC and openHistorian is reachable by an authentica
An authenticated low-privilege user of openPDC can abuse the Modbus connection feature to make outbound connections to a
EUVD-2026-95780
GHSA-cg72-3fmm-q6mm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB