External risk intelligence

OpenPLC Runtime Race Condition Creates Unauthenticated Admin Accounts

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-126088

OpenPLC Runtime is typically used for industrial automation and control systems. While it involves network communication, such systems are generally deployed within isolated internal operational technology (OT) networks rather than being directly exposed to the public internet. Public internet exposure is uncommon for this type of industrial runtime.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A race condition in OpenPLC Runtime allows multiple concurrent requests to create unauthenticated administrator accounts. This vulnerability could allow unauthorized access to control system functions if the affected technology is exposed to external networks. The main concern is confirming relevance and exposure, as these systems are typically isolated.

  • Unauthenticated admin accounts created.
  • Critical for confirming operational technology exposure.
  • Assess operational technology relevance and network exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending multiple concurrent requests to the OpenPLC Runtime over the network. The system's failure to properly check for the existence of users before committing them allows an attacker to bypass authentication and create several unauthenticated administrative accounts. This could potentially lead to unauthorized control or manipulation of the industrial automation system.

  • Unauthenticated network access required.
  • Race condition in user existence check.
  • Risk of unauthorized administrative control.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a race condition in Autonomy Logic OpenPLC Runtime could allow multiple concurrent requests to bypass existence checks, leading to the creation of several unauthenticated administrator accounts. This could potentially grant unauthorized users administrative access to the system.

  • System data and configuration could be at risk.
  • Unauthenticated access could occur over the network.
  • Unauthorized administrative control may result.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Autonomy Logic OpenPLC Runtime vulnerability impacts systems controlling industrial processes. Ownership likely falls to the industrial control system (ICS) or operational technology (OT) teams, possibly with support from infrastructure or vendor management if the product was procured. The immediate first step is to identify all deployed instances of OpenPLC Runtime, determine their network exposure and criticality, and then initiate a coordinated response aligned with operational risk and maintenance schedules.

  • ICS/OT teams own this issue.
  • Verify network exposure and criticality.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Autonomy Logic OpenPLC Runtime?

OpenPLC Runtime is an open-source software component designed for industrial automation and control. It acts as a programmable logic controller (PLC) engine, allowing users to automate processes by running logic scripts. It is commonly deployed in operational technology environments to manage physical machinery and industrial systems, effectively bridging the gap between digital commands and mechanical operations.

What does CWE-362 mean for CVE-2026-126088?

This CVE involves a 'race condition,' which is classified as CWE-362. In this specific case, the software fails to properly coordinate simultaneous requests. Because the system does not finish checking if a user already exists before processing new registration requests, multiple attempts can succeed at once, inadvertently creating unauthorized administrative accounts without requiring valid credentials.

How can an attacker trigger this vulnerability?

The vulnerability is triggered by sending multiple concurrent network requests to the runtime. It is important to note that single, isolated requests will not trigger the bug; the system relies on the race condition occurring during simultaneous traffic. Once the timing window is hit, the application logic fails to block the duplicate creation of administrator privileges.

Is my system at risk if it is not on the internet?

Halo Surface Signal indicates that while this is a network-based issue, OpenPLC Runtime is typically deployed within isolated internal operational technology networks. If your system is not directly exposed to the public internet, the likelihood of an external attacker reaching it is significantly reduced. You should still verify your local network boundaries to ensure internal access is strictly controlled.

What should I do if I use OpenPLC Runtime?

Your first step is to inventory all instances of OpenPLC Runtime within your organization. Once identified, evaluate their specific network connectivity and operational criticality. Consult with your internal industrial control systems or operational technology teams to assess your current exposure and coordinate a response according to your established maintenance and security risk management plans.

References