OpenPLC Runtime race condition lets attackers create admin accounts without authentication
CISA has disclosed a race condition in Autonomy Logic's OpenPLC Runtime up to version 4.2.4 that allows several administrator accounts to be created without authentication. Operators of controllers in manufacturing, energy, transportation and water systems are concerned, and version 4.3.0 fixes the issue.
What to do now
- Product
- Autonomy Logic OpenPLC Runtime
- Affected versions
- OpenPLC Runtime versions 4.2.4 and earlier
- Fixed in
- OpenPLC Runtime 4.3.0 or later
- CVE
- CVE-2026-126088
CISA has issued an industrial control systems advisory for OpenPLC Runtime, the open source programmable logic controller runtime maintained by Autonomy Logic. The flaw, tracked as CVE-2026-126088, affects every release up to and including 4.2.4.
The bug is a classic race condition (CWE-362). The runtime checks whether a user already exists before creating one, but when several requests arrive at the same moment, they can all pass that check before any account is actually saved. The outcome is that multiple administrator accounts can be created by someone who never authenticated.
An attacker who wins the race gains administrative access to the runtime, which effectively means control over the PLC logic it executes. The advisory indicates that exploitation depends on specific timing conditions, but it requires no credentials and no user interaction.
CISA says the product is deployed worldwide, with use in critical manufacturing, energy, transportation systems, and water and wastewater. The advisory does not report active exploitation. The issue was reported by researcher Noureddin Lutfi.
The vendor fix is OpenPLC Runtime 4.3.0. CISA also repeats its standard guidance for control systems: keep them off the internet, place them behind firewalls separated from business networks, and use secured remote access such as an up-to-date VPN when remote administration is needed.
What to do now
- Upgrade every OpenPLC Runtime instance to version 4.3.0 or later.
- Review the administrator accounts on each instance and remove any account you cannot account for.
- Confirm that no OpenPLC Runtime interface is reachable from the internet and keep it behind a firewall, isolated from the business network.
- Require an up-to-date VPN for any remote administration, in line with CISA's general recommended practices.