Skip to main content
Menu
CVEs

Autonomy Logic OpenPLC Runtime race condition in user setup allows admin account creation

Only affects OpenPLC Runtime 4.2.4 and earlier, where concurrent requests can pass the user existence check before any user is committed. Fixed in 4.3.0.

CVE-2026-126088EUVD-2026-130494Published November 19, 2026, updated

8.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.3.0
Who is exposed
Not reported

Summary

Autonomy Logic OpenPLC Runtime is affected. A race condition in its user setup lets an attacker remotely, without logging in, send several requests at once so that multiple unauthenticated administrator accounts get created.

Written by a model

Original description

In Autonomy Logic OpenPLC Runtime versions 4.2.4 and prior, a race condition allows multiple concurrent requests to pass the existence check before any user is committed, resulting in several unauthenticated admin accounts being created.

Who should check

Teams running Autonomy Logic OpenPLC Runtime version 4.2.4 or earlier on industrial control or PLC systems.

“Autonomy Logic OpenPLC Runtime <=4.2.4”

cisa.gov

What to do

Upgrade to a fixed version: 4.3.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126088 (Concurrent Execution using Shared Resource with Improper Synchronization in Autonomy Logic OpenPLC Runtime), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126088 (entry last updated 2026-11-19):
Affected:
- Autonomy Logic OpenPLC Runtime: through 4.2.4
Fixed versions: 4.3.0.
Conditions (all must be true for the bug to be hit):
- OpenPLC Runtime version 4.2.4 or prior (source: https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-01)
- Multiple concurrent requests arrive during the user existence check before any user is committed (source: https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-01)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126088 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126088 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-01
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126088
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126088"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.1/10CVSS 8.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. cve.now early warning

    CISA warns of race condition in Autonomy Logic OpenPLC Runtime 4.2.4 and earlier

  2. CVE published
  3. First seen by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  5. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-126088
RecordNVD · CVE-2026-126088
Other links 1
Linkcisa.gov · news-events/ics-advisories/icsa-26-323-01

Questions about CVE-2026-126088

Is CVE-2026-126088 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A race condition in OpenPLC Runtime lets several requests arrive at the same time and all pass the check that asks whether a user already exists, before any of them is saved. As a result, several unauthenticated admin accounts can be created on the device.

Source: cisa.gov

Which versions are affected by CVE-2026-126088?

OpenPLC Runtime: through 4.2.4.

Source: cve.now feed data

Am I affected, and how do I check?

OpenPLC Runtime version 4.2.4 and prior are affected. To check a device, look at the OpenPLC Runtime version it reports and compare it with 4.2.4.

Source: cisa.gov

How do I fix CVE-2026-126088?

Update to OpenPLC Runtime version 4.3.0 or later, which is the listed fix for this vulnerability.

Source: cisa.gov

No corrections so far. Something wrong on this page? Report an error.