vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-79625

Improper Synchronization in Monitoring in CODESYS Control Runtime

HIGH
8.1
CVSS Score
Published: September 30, 2026 at 09:23 AM UTC
Updated: September 30, 2026 at 07:57 PM UTC
18 products affected across 1 vendorControl for emPC-A/iMX6 SLControl for BeagleBone SLControl for PFC100 SL

Using Control RTE (SL) by CODESYS?

Get instant alerts when new vulnerabilities affect Control RTE (SL) - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH8.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Affected products do not properly synchronize access to their monitoring functionality. When multiple clients send concurrent requests, this may lead to incorrect reads or writes, or to corruption of internal memory structures. An authenticated remote attacker with monitoring access can exploit this issue to cause incorrect data processing or a denial-of-service condition.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Control for BeagleBone SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for emPC-A/iMX6 SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for IOT2000 SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for Linux ARM SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for Linux SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for PFC100 SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for PFC200 SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for PLCnext SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for Raspberry Pi SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement
Control for WAGO Touch Panels 600 SL· Codesys
60%
3.5.0.0 ≤ v < 4.23.0.03.5.0.0
Affected range stops below 4.23.0.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

Source: cverecord
https://www.certvde.com/en/advisories/VDE-2026-097/

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHCERTVDE
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card