HighCVE-2026-79625

    Improper Synchronization in Monitoring in CODESYS Control Runtime (CVE-2026-79625)

    Published Last modified Sources: BSI, CVE.org

    What is affected, what to do

    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.

    Update CODESYS Control RTE (SL) to version 3.5.22.40, CODESYS Control RTE (for Beckhoff CX) SL to version 3.5.22.40, CODESYS Control Win (SL) to version 3.5.22.40.

    Affected
    • CODESYS Control RTE (SL) lt 3.0.0.0..3.5.22.40
    • CODESYS Control RTE (for Beckhoff CX) SL lt 3.0.0.0..3.5.22.40
    • CODESYS Control Win (SL) lt 3.0.0.0..3.5.22.40
    • CODESYS Runtime Toolkit lt 3.0.0.0..3.5.22.40
    • CODESYS Safety SIL2 lt 3.0.0.0..3.5.22.40
    • CODESYS HMI (SL) lt 3.0.0.0..3.5.22.40
    • CODESYS Development System 3 lt 3.0.0.0..3.5.22.40
    • CODESYS Control for BeagleBone SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for emPC-A/iMX6 SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for IOT2000 SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for Linux ARM SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for Linux SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for PFC100 SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for PFC200 SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for PLCnext SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for Raspberry Pi SL lt 3.5.0.0..4.23.0.0
    • CODESYS Control for WAGO Touch Panels 600 SL lt 3.5.0.0..4.23.0.0
    • CODESYS Virtual Control SL lt 3.5.0.0..4.23.0.0
    Fixed in
    • CODESYS Control RTE (SL) 3.5.22.40
    • CODESYS Control RTE (for Beckhoff CX) SL 3.5.22.40
    • CODESYS Control Win (SL) 3.5.22.40
    • CODESYS Runtime Toolkit 3.5.22.40
    • CODESYS Safety SIL2 3.5.22.40
    • CODESYS HMI (SL) 3.5.22.40
    • CODESYS Development System 3 3.5.22.40
    • CODESYS Control for BeagleBone SL 4.23.0.0
    • CODESYS Control for emPC-A/iMX6 SL 4.23.0.0
    • CODESYS Control for IOT2000 SL 4.23.0.0
    • CODESYS Control for Linux ARM SL 4.23.0.0
    • CODESYS Control for Linux SL 4.23.0.0
    • CODESYS Control for PFC100 SL 4.23.0.0
    • CODESYS Control for PFC200 SL 4.23.0.0
    • CODESYS Control for PLCnext SL 4.23.0.0
    • CODESYS Control for Raspberry Pi SL 4.23.0.0
    • CODESYS Control for WAGO Touch Panels 600 SL 4.23.0.0
    • CODESYS Virtual Control SL 4.23.0.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    8.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI, CVE.org

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 13.8

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    72.01 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.1
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.2
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    13.8
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 30 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-362

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: BSI CSAF, BSI WID Portal, NVD (NIST), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    CODESYSControl for BeagleBone SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for emPC-A/iMX6 SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for IOT2000 SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for Linux ARM SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for Linux SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for PFC100 SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for PFC200 SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for PLCnext SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for Raspberry Pi SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl for WAGO Touch Panels 600 SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSControl RTE (for Beckhoff CX) SL
    • 3.0.0.0 – < 3.5.22.40
    • 3.5.22.40
    CODESYSControl RTE (SL)
    • 3.0.0.0 – < 3.5.22.40
    • 3.5.22.40
    CODESYSControl Win (SL)
    • 3.0.0.0 – < 3.5.22.40
    • 3.5.22.40
    CODESYSDevelopment System 3
    • 3.0.0.0 – < 3.5.22.40
    • 3.5.22.40
    CODESYSHMI (SL)
    • 3.0.0.0 – < 3.5.22.40
    • 3.5.22.40
    CODESYSRuntime Toolkit
    • 3.0.0.0 – < 3.5.22.40
    • 3.5.22.40
    CODESYSSafety SIL2
    • 3.0.0.0 – < 3.5.22.40
    • 3.5.22.40
    CODESYSVirtual Control SL
    • 3.5.0.0 – < 4.23.0.0
    • 4.23.0.0
    CODESYSCODESYS Control
    • < 4.23.0.0
    • 4.23.0.0
    CODESYSCODESYS Control RTE (SL)
    • < 3.5.22.40
    • 3.5.22.40
    CODESYSCODESYS Control Win (SL)
    • < 3.5.22.40
    • 3.5.22.40
    CODESYSCODESYS Development System 3
    • < 3.5.22.40
    • 3.5.22.40
    CODESYSCODESYS HMI (SL)
    • < 3.5.22.40
    • 3.5.22.40
    CODESYSCODESYS Runtime Toolkit
    • < 3.5.22.40
    • 3.5.22.40
    CODESYSCODESYS Safety SIL2
    • < 3.5.22.40
    • 3.5.22.40
    CODESYSCODESYS Virtual Control SL
    • < 4.23.0.0
    • 4.23.0.0

    Vendors and products

    Weakness classes (CWE)

    • CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

      Class

      The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

      Entry at MITRE CWE-362

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-79625","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-09-30T13:49:04.420443Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Receivedcert.vde.com

      CVSS V4.0: AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

      CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

      Weakness type: CWE-362

      Description added or changed

      Show 6 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      CVSSadded
      —
      AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
      Weakness type (CWE)added
      —
      CWE-362
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/79xxx/CVE-2026-79625.json">CVE-2026-79625</a>
      Referenceadded
      —
      https://www.certvde.com/en/advisories/VDE-2026-097/

      Source identifier: info@cert.vde.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-79625
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-79625"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-79625.svg?lang=en" alt="CVE-2026-79625 – NEOSEC Intel" height="20"></a>