IPCRIME | November 20, 2026. U.S. cybersecurity officials have issued an industrial-control-system alert about a race condition in Autonomy Logic OpenPLC Runtime that can create unauthorized administrator accounts. The issue, tracked as CVE-2026-126088, affects version 4.2.4 and earlier, according to CISA’s November 19 advisory ICSA-26-323-01.
CISA rates the vulnerability CVSS 8.1 (high) and identifies OpenPLC Runtime 4.3.0 or later as the vendor’s corrective version. Its industrial-sector listing covers deployments in manufacturing, energy, transportation, and water and wastewater systems; that list indicates sectors where the software may appear, not evidence that all facilities in those sectors are affected.
What goes wrong in the application
CISA explains that multiple concurrent requests can pass the application’s administrator-existence check before a new account is actually committed. When that happens, more than one request may create an administrator account without prior authentication. The underlying weakness is a race condition—improper synchronization of shared state—not a generic password weakness.
This matters because administrator creation is a privileged action. A service may appear adequately protected when used normally but fail when competing requests reach a security check simultaneously. The exploitability and consequence in a real installation depend on which interfaces are exposed and the state of the affected software.
Confirmed exposure and exploit status
The affected product is listed as OpenPLC Runtime through 4.2.4, with a documented patch in 4.3.0. CISA credits security researcher Noureddin Lutfi for reporting the weakness. The agency says it had not received reports of known public exploitation specific to this issue when the advisory was released. A CVE and technical proof of a flaw are not proof that a real plant has been breached.
What operators should do
- Inventory each actual OpenPLC Runtime deployment, version, management interface and network zone; do not confuse this component with unrelated OpenPLC products.
- Schedule the official upgrade to 4.3.0 or later, following the release notes and site change-control procedures.
- Review all administrator accounts in affected installations and determine whether unexpected accounts were created or retained.
- Limit management interfaces to approved operator networks and restrict Internet reachability. Use network segmentation and monitored remote-access paths.
- Validate control-system behavior in a representative test environment before changing production systems, then document the installed version and account audit results.
A wider identity-control lesson
Creation of a privileged first user is a particularly sensitive point in many tools, especially interfaces initially deployed in a lab and later exposed in operational environments. Teams should test how bootstrap accounts are created, disable unused setup paths when possible, and verify that adding administrators always requires approved authorization.
Source and further reading
CISA industrial advisory ICSA-26-323-01 (November 19); CISA official machine-readable advisory; OpenPLC Runtime maintained source project.