CISA Advises OpenPLC Runtime 4.3.0 for Unauthenticated Admin Creation
Quick Answer
Identify OpenPLC Runtime 4.2.4 or earlier, plan the supported 4.3.0 update, and review administrator accounts and exposed management paths.
Confirm Scope And Apply The Supported Remediation
What to do now: Record runtime versions, management endpoints, network exposure, responsible control-system owners and available recovery procedures. Validate whether the vulnerable runtime is deployed and reachable. CISA’s public-exploitation statement does not establish that a particular controller is uncompromised. Upgrade to OpenPLC Runtime 4.3.0 or later through the approved OT change process. Restrict management access and isolate control networks according to the operational risk assessment. Review unexpected administrator accounts, test authentication and representative control functions in a safe maintenance window, and retain configuration backups and before-and-after evidence.
Last verified: 2026-11-19 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Autonomy Logic OpenPLC Runtime |
|---|---|
| Advisory | ICSA-26-323-01 |
| CVE | CVE-2026-126088 |
| Authoritative release date | 2026-11-19 — displayed CISA release date; the page release metadata is 2026-11-19T12:00:00Z. |
| Authority revision date | CISA revision history records revision 1, Initial Publication, on November 19, 2026. |
| Affected versions | OpenPLC Runtime 4.2.4 and earlier. Concurrent requests can pass the user-existence check before a user is committed, allowing unauthenticated administrator accounts to be created. |
| Fixed version | OpenPLC Runtime 4.3.0 or later |
| CVSS base score | 9.2 (CVSS v4.0); 8.1 (CVSS v3.1) |
| CVSS severity | Critical (v4.0); High (v3.1) |
| Exploitation status | CISA states that no known public exploitation specifically targeting these vulnerabilities has been reported to it at publication.; no exploitation claim is inferred. |
What Changed
CISA disclosed a race condition in OpenPLC Runtime account creation and directs users to version 4.3.0 or later. The issue crosses the administrative-access boundary; exposure depends on reachable vulnerable runtime services.
What To Validate Now
- Inventory. Record runtime versions, management endpoints, network exposure, responsible control-system owners and available recovery procedures.
- Establish applicability. Validate whether the vulnerable runtime is deployed and reachable. CISA’s public-exploitation statement does not establish that a particular controller is uncompromised.
- Remediate. Upgrade to OpenPLC Runtime 4.3.0 or later through the approved OT change process. Restrict management access and isolate control networks according to the operational risk assessment.
- Validate. Review unexpected administrator accounts, test authentication and representative control functions in a safe maintenance window, and retain configuration backups and before-and-after evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Coordinate downtime and safety review with the control-system owner. Do not test account-creation races against a running production process.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

