As reported by CISA in advisory ICSA-26-323-01, a race condition vulnerability in Autonomy Logic's OpenPLC Runtime could allow attackers to create multiple unauthenticated admin accounts on affected systems. This advisory is particularly notable because OpenPLC is an open-source PLC runtime increasingly adopted in budget-constrained industrial environments — precisely the deployments that often lack dedicated security teams and rapid patch cycles.

Security Impact: As reported by CISA in advisory ICSA-26-323-01, a race condition vulnerability in Autonomy Logic's OpenPLC Runtime could allow attackers to create multiple unauthenticated admin accounts on affected systems.

Vulnerability Details

CVE IDCVE-2026-126088
CVSS v3.18.1 (HIGH) — AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.09.2 (CRITICAL)
CWECWE-362: Race Condition
Affected ProductOpenPLC Runtime <= 4.2.4
VendorAutonomy Logic (US-headquartered)
Patch StatusFixed in version 4.3.0
Active ExploitationNot confirmed in the wild at time of advisory

Why This Matters

The vulnerability exploits a classic TOCTOU (time-of-check-to-time-of-use) race condition. Multiple concurrent registration requests can bypass the user existence check before any single request commits, resulting in the creation of unauthorized admin accounts. While the attack vector requires network access and the CVSS v3.1 scoring reflects high attack complexity, the CVSS v4.0 score of 9.2 underscores the severity when accounting for modern threat metrics.

What elevates this beyond a mundane web vulnerability is the deployment context. OpenPLC is used across Critical Manufacturing, Energy, Transportation Systems, and Water/Wastewater sectors. A compromised PLC runtime in any of these environments can translate to physical process manipulation — not just data exfiltration. An attacker with admin-level access to a PLC runtime can modify ladder logic, alter setpoints, or disable safety interlocks.

OpenPLC's open-source nature and low cost make it attractive to smaller utilities and manufacturers who may not have the OT security maturity of large enterprises. These organizations frequently deploy PLCs with internet-facing management interfaces, exactly the scenario CISA's advisory implicitly warns against.

Broader Implications for OT Security

  • Open-source ICS components are a double-edged sword: While transparency enables faster vulnerability discovery, patch adoption in OT environments lags significantly behind IT — often by months or years due to change-control constraints and uptime requirements.
  • Race conditions in authentication flows are underreported in ICS: Many ICS web interfaces were built without considering concurrent request handling, and this class of vulnerability likely exists in other products beyond OpenPLC.
  • Account creation flaws bypass network segmentation: Even if an attacker cannot directly manipulate PLC logic, gaining admin credentials provides persistence that survives network reconfiguration and firewall rule updates.

Who Is at Risk

Organizations running OpenPLC Runtime 4.2.4 or earlier with the management interface exposed on any reachable network are at highest risk. This is especially dangerous for small-to-midsize water utilities, distributed energy resources, and light manufacturing facilities that adopted OpenPLC for cost reasons and may lack VLAN segmentation between IT and OT networks.

Even a high-complexity attack becomes trivial when the target is a single-purpose device with a predictable IP, default credentials, and no intrusion detection.

Shield53 Recommendations

Immediate Actions

Who Is at Risk
Patch now: Upgrade to OpenPLC Runtime 4.3.0 or later immediately. Download only from the official OpenPLC GitHub repository.
Isolate the management interface: Ensure the OpenPLC web management port is not accessible from the internet or the corporate IT network. Place it behind a firewall on a dedicated OT VLAN.
Audit existing accounts: Review all user accounts on every OpenPLC instance. Remove any accounts that cannot be attributed to a known administrator. Document baseline account state for future comparison.
Restrict network exposure: If remote access is required, use a hardened VPN with MFA — not port forwarding or direct internet exposure. Limit VPN access to specific source IPs where possible.

Detection Guidance

  • Monitor OpenPLC web server logs for bursts of concurrent POST requests to the user registration or account creation endpoints — this pattern is indicative of race condition exploitation attempts.
  • Deploy network-based detection for repeated authentication attempts or account creation requests originating from non-administrative IP ranges.
  • Configure file integrity monitoring on OpenPLC configuration files to alert on unauthorized modifications to ladder logic programs or system settings.

Hardening Posture

  • Disable the web management interface on production PLCs if programmatic management is not required; use serial or local network programming instead.
  • Implement network-level authentication (mTLS or IP allowlisting) in front of the OpenPLC management interface using a reverse proxy.
  • Schedule quarterly account audits on all ICS assets, not just OpenPLC. Treat user account databases as safety-critical configuration.

This advisory is a reminder that authentication mechanisms in ICS software deserve the same scrutiny as the control logic itself. A vulnerability in the login page can be just as damaging as a flaw in the safety interlock — both can lead to loss of view, loss of control, and ultimately, physical consequences.