openPDC: Use of Externally-Controlled Input to Select Classes or Code
CVE-2026-104629 is a high-severity use of externally-controlled input to select classes or code vulnerability in openPDC from Grid Protection Alliance, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 2.9.477, 2.9.482 as the first without the flaw, so updating openPDC to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.34% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update openPDC to 2.9.477 or 2.9.482, whichever matches your release line, or a later version.
- Update openPDC (Docker image) to 2.9.477 or 2.9.482, whichever matches your release line, or a later version.
- Update openHistorian to 2.8.580 or 2.8.585, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Grid Protection Alliance | openPDC | before 2.9.477; before 2.9.482 | 2.9.477, 2.9.482 |
| Grid Protection Alliance | openPDC (Docker image) | before 2.9.477; before 2.9.482 | 2.9.477, 2.9.482 |
| Grid Protection Alliance | openHistorian | before 2.8.580; before 2.8.585 | 2.8.580, 2.8.585 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (hq.dhs.gov).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.7 | High | CNA (hq.dhs.gov) |
| CVSS 3.1 | 8.8 | High | CNA (hq.dhs.gov) |
Official description
A component loading mechanism in openPDC and openHistorian will construct and run any specified type, which may be an invalid component to load. An attacker with an authenticated user account and the ability to place a file on the host filesystem can use this to run arbitrary constructor code, and this code runs with the privileges of the affected service account.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Externally-Controlled Input to Select Classes or Code
The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.
How developers prevent this class of flaw
- Refactor your code to avoid using reflection.
- Do not use user-controlled inputs to select and load classes or code.
- Apply strict input validation by using allowlists or indirect selection to ensure that the user is only selecting allowable classes or code.
More Use of Externally-Controlled Input to Select Classes or Code vulnerabilities (CWE-470)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Other references
Other vulnerabilities in openPDC
- 7.5 High severity
- 9.8 Critical severity
Recent Use of Externally-Controlled Input to Select Classes or Code vulnerabilities
- 7.8 High severity
- 8.5 High severity
- 7.5 High severity
- 7.2 High severity
- 7.8 High severity
- 8.2 High severity
Spotted an error? Tell us.