CISA warns of OpenPLC Runtime race condition enabling admin accounts

src-8b712f9c

CISA has warned that a race condition in Autonomy Logic OpenPLC Runtime could let unauthenticated requests create multiple administrator accounts. The issue, tracked as CVE-2026-126088, affects versions 4.2.4 and earlier. The agency’s advisory was published November 19, 2026.

The flaw arises when concurrent requests check whether an account exists before any account creation has been committed. Under that timing condition, several requests can pass the check and result in multiple unauthenticated administrator accounts. CISA says successful exploitation could therefore give an attacker administrative access.

Severity and affected versions

CISA lists the affected product as Autonomy Logic OpenPLC Runtime versions 4.2.4 and earlier, with the product status marked known affected. The vulnerability is categorized as CWE-362, concurrent execution using a shared resource with improper synchronization, commonly described as a race condition.

The advisory gives the issue a CVSS 3.1 score of 8.1, rated High, and a CVSS 4.0 score of 9.2, rated Critical. The CVSS 3.1 vector indicates network reachability and no required privileges or user interaction, while also specifying high attack complexity. The separate CVSS 4.0 assessment includes an attack-requirements condition. These scores reflect different versions of the scoring standard; defenders should consult the advisory’s vectors when evaluating the issue against their own environments.

Update and reduce exposure

The recommended remediation is to upgrade to OpenPLC Runtime 4.3.0 or later. Organizations should identify deployments running affected releases and plan updates in accordance with operational requirements. Because this software may be used in industrial control environments, CISA advises performing an impact analysis and risk assessment before deploying defensive measures.

CISA recommends minimizing network exposure for control-system devices and ensuring they are not accessible from the internet. Control-system networks and remote devices should be placed behind firewalls and isolated from business networks. Where remote access is necessary, the agency recommends more secure methods such as virtual private networks, while cautioning that VPN products also require updates and that a VPN’s security depends in part on the devices connected through it.

Industrial environments should verify access paths

The advisory identifies critical manufacturing, energy, transportation systems, and water and wastewater systems as relevant sectors, and says the product is deployed worldwide. Operators in those environments should establish whether affected runtime instances are present, review how they can be reached, and prioritize remediation according to exposure and operational risk.

CISA reported no known public exploitation specifically targeting this vulnerability at the time of publication. That statement does not establish that affected systems are safe from future attempts, and the lack of reported exploitation is not a substitute for patching or limiting access. Organizations that observe suspected malicious activity should follow their internal response procedures and report findings to CISA for tracking and correlation.

The vulnerability was reported to CISA by Noureddin Lutfi. In addition to patching and network segmentation, operators can use the agency’s industrial control system security guidance to support defense-in-depth planning. The immediate priorities are to confirm product versions, upgrade affected deployments, and ensure control systems are not unnecessarily exposed to external or business networks.