cve.bz

CVE-2026-79625 codesys: Race Condition

7.2 highEPSS 0.2%

High (7.2) in codesys. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.2 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-79625 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79625?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79625?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-79625 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • codesys:control for beaglebone sl
  • codesys:control for empc-a/imx6 sl
  • codesys:control for iot2000 sl
  • codesys:control for linux arm sl
  • codesys:control for linux sl
  • codesys:control for pfc100 sl
  • codesys:control for pfc200 sl
  • codesys:control for plcnext sl
  • codesys:control for raspberry pi sl
  • codesys:control for wago touch panels 600 sl
  • codesys:control rte (for beckhoff cx) sl
  • codesys:control rte (sl)
  • codesys:control win (sl)
  • codesys:development system 3
  • codesys:hmi (sl)
  • codesys:runtime toolkit
  • codesys:safety sil2
  • codesys:virtual control sl

Versions

From the CNA's record in the CVE List.

ProductAffected
CODESYS Control RTE (SL)from 3.0.0.0 before 3.5.22.40
CODESYS Control RTE (for Beckhoff CX) SLfrom 3.0.0.0 before 3.5.22.40
CODESYS Control Win (SL)from 3.0.0.0 before 3.5.22.40
CODESYS Runtime Toolkitfrom 3.0.0.0 before 3.5.22.40
CODESYS Safety SIL2from 3.0.0.0 before 3.5.22.40
CODESYS HMI (SL)from 3.0.0.0 before 3.5.22.40
CODESYS Development System 3from 3.0.0.0 before 3.5.22.40
CODESYS Control for BeagleBone SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for emPC-A/iMX6 SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for IOT2000 SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for Linux ARM SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for Linux SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for PFC100 SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for PFC200 SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for PLCnext SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for Raspberry Pi SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Control for WAGO Touch Panels 600 SLfrom 3.5.0.0 before 4.23.0.0
CODESYS Virtual Control SLfrom 3.5.0.0 before 4.23.0.0

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON