CODESYS runtime vulnerabilities reach far past one brand: as of 2026-11-18, CERT@VDE lists 38 advisories for CODESYS GmbH, and the same CODESYS Control V3 runtime runs inside PLCs, drives and operator panels from WAGO, Schneider Electric, ABB, Rockwell Automation and Festo. Triage starts with the runtime version on each controller, which the device vendor's firmware hides behind its own numbers. Then check which CVE family applies, apply the vendor's firmware, and enforce user management, encrypted communication and firewall rules for ports 11740 and 1217.
Key takeaways
- CODESYS Control is a runtime that turns an embedded or PC-based device into an IEC 61131-3 programmable controller, and device makers license it rather than writing their own.
- Ask the running controller first, then confirm against the vendor's release notes.
- Most CODESYS runtime CVEs fall into four families: memory errors in the protocol servers, flaws reachable without a login, abuse of features by a logged-in user, and weaknesses in the web server and gateway.
- Vendor and CERT advisories name the devices, and they are the most reliable list, because a vendor's product page rarely mentions CODESYS.
What is the CODESYS runtime, and why does one bug reach many vendors?
CODESYS Control is a runtime that turns an embedded or PC-based device into an IEC 61131-3 programmable controller, and device makers license it rather than writing their own. CODESYS's Advisory 2023-02 describes it as the system that "enables embedded or PC-based devices to be a programmable industrial controller", with communication servers for the CODESYS protocol so that the CODESYS Development System and HMIs can log in, download applications and read variables. Microsoft's 2023 research post cites CODESYS's own figure of approximately 1,000 device types from over 500 manufacturers.
The runtime ships in several forms, and the version numbers differ:
| Form | Examples from CODESYS advisories | Version line | Who patches it |
|---|---|---|---|
| CODESYS Runtime Toolkit (Control V3 Runtime System Toolkit in older advisories) | Built into a vendor's own PLC, drive or HMI firmware | 3.5.x.y, such as 3.5.19.0 | The device vendor, in a firmware release |
| CODESYS SL products | Control for Linux SL, for PFC200 SL, for PLCnext SL, for Raspberry Pi SL, for IOT2000 SL, Virtual Control SL | 4.x.y.z, such as 4.8.0.0 | The user, from the CODESYS Store or Installer |
| PC runtimes | Control Win (SL), Control RTE (SL), Control RTE (for Beckhoff CX) SL | 3.5.x.y | The user |
The two numbering lines meet in the advisories. Advisory 2023-02 says CODESYS released "version V4.8.0.0 based on the CODESYS Control V3 Runtime System Toolkit V3.5.19.0" for the SL products, so 4.8.0.0 and 3.5.19.0 carry the same fixes. A controller with a vendor firmware number such as FW25 tells you neither.
How do you find the CODESYS runtime version in a device?
Ask the running controller first, then confirm against the vendor's release notes. Four methods, from least to most effort:
Communication Settings scanIn the CODESYS Development System, the Communication Settings tab scans the network and lists, per device, the Target vendor, Target ID, Target name, Target type and Target version, and whether communication is encrypted. PLC shellAfter login, the PLC shell command rtsinfo"provides information about the runtime system, for example the processor and version of the runtime system". The same shell'schannelinfocommand gives information about the communication channel.Microsoft's version toolMicrosoft's CoDe16 repository, archived and MIT-licensed, contains an "active tool to extract the CODESYS V3 runtime version of devices", a Wireshark dissector for the CODESYS V3 protocol and the full white paper. It sends requests to the device, so run it in a maintenance window. Firmware image and vendor notesIn an unpacked Linux-based firmware image, a CODESYSControl.cfgconfiguration file and component names such as CmpApp, CmpUserMgr or CmpWebServer show that the runtime is present; CODESYS advisories name both. The version itself is best taken from the running device or from the vendor's release notes, because the vendor's advisory is the only source that says which CODESYS fixes a firmware release includes.
Record the result as two fields: the vendor firmware version and the CODESYS runtime version. Our firmware SBOM guide covers keeping both in a component inventory.
Which CODESYS CVE families matter for a controller?
Most CODESYS runtime CVEs fall into four families: memory errors in the protocol servers, flaws reachable without a login, abuse of features by a logged-in user, and weaknesses in the web server and gateway. The table lists the runtime CVEs most likely to appear in a scan, with the fixed versions from the CODESYS advisory or CERT@VDE.
| CVE | Component and issue | Login needed? | CVSS v3.1 (source) | Fixed in Runtime Toolkit / SL | Advisory |
|---|---|---|---|---|---|
| CVE-2022-47379 to CVE-2022-47390 | CmpApp, CmpAppForce, CmpTraceMgr out-of-bounds and stack writes (Microsoft) | Yes | 8.8 (CERT@VDE) | 3.5.19.0 / 4.8.0.0 | CODESYS 2023-02 |
| CVE-2022-47391 | CmpDevice invalid read, denial of service | No | 7.5 (CERT@VDE) | 3.5.19.0 / 4.8.0.0 | CODESYS 2023-03 |
| CVE-2023-37545 to CVE-2023-37559 | CmpApp, CmpAppBP, CmpAppForce invalid reads and a heap write, denial of service | Yes | 6.5 (CERT@VDE) | 3.5.19.20 / 4.10.0.0 | VDE-2023-019 |
| CVE-2022-4046 | Application code not restricted to application memory | Yes (programmer) | 8.8 (CERT@VDE) | All versions; mitigated by user management and enforced signing | VDE-2023-025 |
| CVE-2023-6357 | OS command injection through SysFile or CAA File libraries, Linux and QNX only | Yes (programmer) | 8.8 (CERT@VDE) | 3.5.19.50 / 4.11.0.0 | VDE-2023-066 |
| CVE-2020-10245 | CODESYS V3 web server buffer overflow | No | 9.8 (NVD) | 3.5.15.40 | CODESYS advisory linked from NVD |
| CVE-2024-8175 | CmpWebServer crash on a crafted TLS packet | No | 7.5 (CERT@VDE) | 3.5.20.30 / 4.14.0.0 | VDE-2024-057 |
| CVE-2025-41659 | PKI folder readable and writable over the CODESYS protocol | Yes (low privilege) | 8.3 (CERT@VDE) | 3.5.21.20 / 4.17.0.0 | VDE-2025-051 |
| CVE-2025-41691 | CmpDevice NULL pointer dereference in 3.5.21.10 and 4.16.0.0 only | No | 7.5 (CERT@VDE) | 3.5.21.20 / 4.17.0.0 | VDE-2025-070 |
| CVE-2025-41660 | Service-group user can replace the boot application | Yes (low privilege) | 8.8 (CERT@VDE) | 3.5.22.0 / 4.21.0.0 | VDE-2026-011 |
| CVE-2026-3509 | Format string in the Audit Log, denial of service | No | 7.5 (CERT@VDE) | 3.5.22.0 / 4.21.0.0 | VDE-2026-018 |
| CVE-2026-8047 | CmpWebServer out-of-bounds write on a crafted HTTP request | No | 7.5 (CVSS v4.0 8.7) | 3.5.22.20 / 4.21.0.0 | VDE-2026-057 |
| CVE-2026-79625 | CmpMonitor2 race between concurrent monitoring clients | Yes (monitoring) | 8.1 (CVSS v4.0 7.2) | 3.5.22.40 / 4.23.0.0 | VDE-2026-097 |
The SL column gives the Control for Linux SL fix; the other SL runtimes received the same 4.x version in older advisories, but since 2026 CERT@VDE lists only Control for Linux SL and Virtual Control SL among the SL products.
Microsoft's 2023 findings: tag decoding in the protocol servers
Microsoft reported the vulnerabilities to CODESYS in September 2022 after studying the CODESYS V3 protocol on two controllers, a Schneider Electric Modicon TM251 and a WAGO PFC200. Its post says the tag-decoding code copied "the whole tag" into a buffer "without validating the size", and that "fifteen places in CODESYS V3 SDK were found with the same issue". The researchers "were able to apply 12 of the buffer overflow vulnerabilities to gain RCE" on both PLCs.
The login requirement did not stop them. Microsoft used CVE-2019-9013, which NVD describes as credentials "insufficiently protected during transport" because of non-TLS encryption, to replay a captured username and password hash and log in. Advisory 2023-02 rates the set high with CVSS 3.1 base score 8.8 and credits Vladimir Tokarev of Microsoft; CVE-2022-47391, the unauthenticated CmpDevice bug from the same research, has its own Advisory 2023-03 at 7.5. Microsoft's table gives 8.8 for CVE-2022-47392 and CVE-2022-47393, while CODESYS and NVD score both 6.5 because they only cause a denial of service; use the CODESYS score. The same advisory covers CVE-2022-47378, in which crafted requests after login make the CmpFiletransfer component read from an invalid address; it only stops the runtime, and NVD scores it 6.5.
Flaws reachable without a login
User management does not help against the CVEs in the "No" rows. CVE-2022-47391, CVE-2025-41691 and CVE-2026-3509 crash the runtime through the CODESYS protocol itself, and CVE-2020-10245, CVE-2024-8175 and CVE-2026-8047 hit the web server that serves WebVisu screens. VDE-2026-057 says the runtime is only affected when "the web server is active, which by default requires a running application with an enabled Web Visualization", so a controller without WebVisu has less exposure. For these, the firewall and the patch are the controls.
Abuse of features by a logged-in user
A second group turns legitimate programming rights into control of the device. CVE-2023-6357 lets a programmer "inject calls to additional operating system shell functions" through file libraries on Linux and QNX. CVE-2025-41660 lets a user in the restricted Service group install "a new boot application without requiring any cryptographic validation, if the application signing is not enforced". CVE-2022-4046 has no fixed version at all: VDE-2023-025 lists all versions as affected and relies on online user management and "Enforced Signing" of application code.
Which vendors embed the CODESYS runtime?
Vendor and CERT advisories name the devices, and they are the most reliable list, because a vendor's product page rarely mentions CODESYS. The table covers advisories that state the CODESYS link directly.
| Vendor | Products named | Advisory | What the vendor says to do |
|---|---|---|---|
| WAGO | PFC100, PFC200, Compact Controller 100, EC 300, TP 600, firmware up to FW25 | VDE-2023-026 | Activate "port authentication" in web-based management, change the default admin password, deactivate the CODESYS programming port if commissioning is finished |
| Schneider Electric | Modicon M241, M251, M258, M262, LMC058, LMC078, PacDrive 3 LMC Eco/Pro/Pro2, Harmony and Magelis HMIs | ICSA-26-020-02 (SEVD-2023-192-04) | Firmware delivered with EcoStruxure Machine Expert v2.2; migrate end-of-life M218 and Magelis XBT, which receive no fix |
| Rockwell Automation | LP30, LP40, LP50 and BM40 operator panels | ICSA-24-030-07 | Upgrade the CODESYS version; Rockwell's text names 3.5.19.2 |
| ABB | ACS880 drives | ICSA-25-093-03 | Latest firmware disables IEC online programming communication by default |
| ABB | AC500 V3 PLCs | ICSA-26-132-03 | Firmware 3.9.0 fixes CVE-2025-2595, CVE-2025-41659 and CVE-2025-41691 |
| Festo | CECC-S, CECC-LK and CECC-D controllers | ICSA-25-273-04 | Firmware 2.4.2.0 for the fixes listed per CVE |
Two patterns stand out. First, vendors lag CODESYS: Schneider's notice was first released on 11 July 2023 and revised through December 2025 as fixes reached each product line, and CISA republished it on 20 January 2026. Second, the CODESYS SL products for third-party hardware, such as Control for PFC200 SL or Control for PLCnext SL, are CODESYS products patched by CODESYS, not by WAGO or Phoenix Contact.
Why do scanners miss CODESYS CVEs?
Version-based scanners depend on NVD CPE data, and for CODESYS that data names CODESYS products, not the vendor devices. NVD's record for CVE-2022-47379 lists CPEs such as codesys:control_runtime_system_toolkit before 3.5.19.0 and codesys:control_for_pfc200_sl before 4.8.0.0; a WAGO PFC200 with firmware FW25 matches neither. As of 2026-11-18, every 2024 to 2026 CODESYS runtime CVE in the table above is Deferred or Awaiting Analysis in NVD, with no CPE configuration at all, so a CPE-only scan finds none of them.
Use the CERT@VDE advisories for the CODESYS side, since each one links a CSAF document with machine-readable product and version data, and the vendor or CISA advisory for the device side. Our CSAF and VEX guide explains the format.
How should KEV and EPSS weigh in on CODESYS findings?
As of 2026-11-18, CISA's KEV catalog (version 2026.11.13, 1,781 entries) lists no CODESYS CVE. As of the same date, the latest FIRST EPSS scores, dated 2026-11-17, were:
| CVE | EPSS | Percentile |
|---|---|---|
| CVE-2020-10245 | 0.029 | 0.873 |
| CVE-2022-47379 | 0.020 | 0.808 |
| CVE-2022-47391 | 0.019 | 0.796 |
| CVE-2022-47380, CVE-2022-47381 | 0.013 | 0.714 |
| CVE-2023-6357 | 0.010 | 0.621 |
| CVE-2024-8175 | 0.006 | 0.504 |
| CVE-2025-41691 | 0.006 | 0.512 |
| CVE-2026-8047 | 0.004 | 0.393 |
The CODESYS advisories for the Microsoft findings state that "no known public exploits specifically target these vulnerabilities in CODESYS products". Low EPSS scores reflect how rarely these CVEs show up in internet-wide exploitation data, not the impact on one exposed controller. Rank by reachability first: unauthenticated CVEs on a controller that any host can reach on 11740 or the web port come before authenticated ones behind enforced user management. Our KEV and EPSS prioritization guide covers the method.
How do you patch and harden a CODESYS-based controller?
Patch through the device vendor, and harden the runtime settings in the meantime. Most hardening is set on the Communication Settings tab or in the runtime's CODESYSControl.cfg.
Enforce online user managementAdvisory 2023-02 says "a successful login to the affected product is required" for its CVEs and that "as of version V3.5.17.0, the online user management is enforced by default". On older runtimes, or where it was switched off, turn it on, set strong passwords and give engineers individual accounts. Keep the Service group free of boot-application rights unless needed. Enforce encrypted communicationThe Communication Settings help lists three policies: "No encryption", "Optional encryption" and "Enforced encryption: The device supports encrypted communication only". Choose enforced encryption, which closes the credential capture Microsoft used through CVE-2019-9013. Enforce signed application codeSet the code-signing policy to enforced signing; VDE-2026-011 gives the runtime setting SECURITY.EnforceSignedCode=YESin the[CmpApp]section as the mitigation for CVE-2025-41660, and VDE-2023-025 names enforced signing for CVE-2022-4046.Block legacy loginsVDE-2025-070 mitigates CVE-2025-41691 by setting SECURITY.UserLogin_AuthenticationType=ONLY_ASYMMETRICin[CmpUserMgr], which also blocks CODESYS clients older than 3.5.16.0.Switch off what is not usedDisable WebVisu and the web server if no browser HMI is needed; VDE-2026-018 shows how to disable the Audit Log logger as a workaround for CVE-2026-3509; WAGO recommends deactivating the CODESYS programming port after commissioning. Patch through the vendorMap each controller's vendor firmware to the CODESYS fixes in the vendor advisory. For SL products, update from the CODESYS Store or Installer. Our IEC 62443-2-3 patch management guide covers testing and scheduling updates for running plants.
Firewall rules for ports 11740, 1740 and 1217
Microsoft's research lists the CODESYS V3 protocol on "ports 11740-11743 for TCP" and "ports 1740-1743 for UDP", and Schneider's advisory tells users of the Modicon M241, M251, M258, M262, LMC058 and PacDrive 3 controllers to "restrict access to programming ports, typically UDP/1740, TCP/11740 and TCP/1105" (TCP/484 for the Easy Modicon M310). The CODESYS Gateway uses port 1217: VDE-2025-013 says "by default, the CODESYS Gateway listens on all available network adapters on port 1217", which lets an unauthenticated attacker scan the PLC network behind an engineering PC (CVE-2024-41975, CVSS 5.3). Gateway for Windows 3.5.21.0 fixes the default.
| Port | Service | Allow from |
|---|---|---|
| TCP 11740 to 11743 | CODESYS V3 protocol on the controller | Named engineering workstations and HMIs only |
| UDP 1740 to 1743 | CODESYS V3 protocol, including device scans | Engineering workstations in the same zone only |
| TCP 1217 | CODESYS Gateway on an engineering PC or edge device | Local host only; on older Windows gateways set LocalAddress=127.0.0.1 in [CmpGwCommDrvTcp] |
| HTTP/HTTPS web ports | CmpWebServer for WebVisu | HMI clients only, or closed if WebVisu is unused |
None of these ports belongs on the internet or in the office network. Place controllers in their own zone as described in the Purdue model guide, and use a VPN for remote access, as the CODESYS advisories recommend.
What does a CODESYS triage of one machine look like? (worked example)
Synthetic example. The machine, addresses and findings are invented for illustration; the CVEs and versions come from the advisories above.
A packaging machine builder lists the controllers in one line: a WAGO PFC200 with firmware FW24, a Raspberry Pi running CODESYS Control for Raspberry Pi SL 4.7.0.0 for data logging, and an engineering laptop with the CODESYS Development System. The Communication Settings scan and rtsinfo confirm the versions.
| Device | Finding | Action |
|---|---|---|
| WAGO PFC200, FW24 | In VDE-2023-026 scope (up to FW25); Microsoft CVEs apply | Update to the current WAGO firmware; activate port authentication; change the admin password |
| Control for Raspberry Pi SL 4.7.0.0 | Below 4.8.0.0, so the 2023-02 and 2023-03 CVEs apply, as do later fixes up to 4.17.0.0 | Update from the CODESYS Store; enforce encryption and user management |
| Engineering laptop | Gateway reachable on port 1217 from the plant network | Update the Gateway to 3.5.21.0 or later, or bind it to 127.0.0.1 |
The builder then closes TCP 11740 and UDP 1740 on the cell switch to everything except the laptop and the HMI.
What are the common pitfalls?
- Reading the vendor firmware number as the CODESYS version. FW25 or 3.9.0 says nothing about CODESYS until the vendor advisory maps it.
- Assuming user management covers everything. Several runtime CVEs, including CVE-2022-47391, CVE-2024-8175 and CVE-2026-8047, need no login.
- Leaving encryption optional. Optional encryption still accepts unencrypted logins, the path Microsoft used to capture credentials.
- Forgetting the engineering PC. The Gateway on port 1217 and the simulation runtime in the Development System are affected too.
- Relying on CPE matching alone. Recent CODESYS CVEs have no NVD configuration, and device firmware never matches a CODESYS CPE.
For protocol-level monitoring of other controllers on the same network, see the S7comm and OPC UA guides, and map attacker techniques with MITRE ATT&CK for ICS.
AI-assisted analysis: what SoftWSP actually runs
SoftWSP identifies software components and versions in a firmware image or a component list, and matches them against NVD, CISA KEV, FIRST EPSS and CISA's ICS advisories with deterministic code; a watchlist can alert on a vendor product or a CVE. AI then writes the plain-language summary, citing the component, version and record behind each finding, and an engineer reviews every report before it is sent.
For CODESYS-based controllers, the useful input is the device model, the vendor firmware version and, where known, the CODESYS runtime version. The judgements this guide describes as manual stay with the engineer: which CODESYS fixes a vendor firmware contains, whether a CVE with no NVD configuration applies, and whether user management, encrypted communication, signed code and firewall rules are in force on the running controller. For a machine line, see the machine builder report.
This guide draws on CODESYS Advisories 2023-02 and 2023-03, the CERT@VDE CODESYS advisory list and advisories VDE-2023-019, -025, -026, -066, VDE-2024-057, VDE-2025-013, -051, -070 and VDE-2026-011, -018, -057, -097, Microsoft's August 2023 research post and CoDe16 repository, CISA advisories ICSA-24-030-07, ICSA-25-093-03, ICSA-25-273-04, ICSA-26-020-02 and ICSA-26-132-03, the CODESYS online help, NVD records, CISA's KEV catalog version 2026.11.13 and FIRST EPSS data dated 2026-11-17, all read on 2026-11-18.
Put this guide to work
Frequently asked questions
How do I find which CODESYS runtime version a PLC is running?
Ask the device first, then confirm with the vendor. In the CODESYS Development System, the Communication Settings scan lists each controller's Target vendor, Target name and Target version, and the PLC shell command rtsinfo returns information about the runtime system, including its version. Microsoft's open-source CoDe16 repository also contains an active tool that extracts the CODESYS V3 runtime version from devices. Then read the device vendor's firmware release notes or security advisory, because vendors number firmware their own way (WAGO uses FW25, ABB AC500 V3 uses 3.9.0) and only the vendor states which CODESYS fixes a firmware release contains.
What did Microsoft's 2023 CODESYS research find?
Microsoft's cyber-physical systems researchers reported 16 vulnerabilities in the CODESYS V3 runtime to CODESYS in September 2022 and published their research in August 2023. Fifteen are covered by CODESYS Advisory 2023-02 (CVE-2022-47378 to CVE-2022-47390, CVE-2022-47392 and CVE-2022-47393) and one, CVE-2022-47391 in CmpDevice, by Advisory 2023-03. Most are memory errors in the tag decoding of the CODESYS protocol in components such as CmpApp, CmpAppForce and CmpTraceMgr. They need a logged-in user, but Microsoft chained an older credential flaw, CVE-2019-9013, to get past the login and achieved remote code execution on a Schneider Electric Modicon TM251 and a WAGO PFC200. CODESYS fixed them in version 3.5.19.0, and in 4.8.0.0 for the SL runtimes.
Which ports does a CODESYS controller use, and which should a firewall block?
Microsoft's research describes the CODESYS V3 protocol on TCP ports 11740 to 11743 and UDP ports 1740 to 1743. Schneider Electric's advisory for its CODESYS-based controllers tells users of the Modicon M241, M251, M258, M262, LMC058 and PacDrive 3 controllers to restrict the programming ports, typically UDP/1740, TCP/11740 and TCP/1105 (TCP/484 for the Easy Modicon M310). The CODESYS Gateway, which relays engineering traffic to controllers, listens on port 1217, and CERT@VDE advisory VDE-2025-013 says Gateway for Windows versions before 3.5.21.0 listen on all network adapters by default. Allow these ports only from named engineering workstations and HMIs, never from the internet or the office network.
Is any CODESYS vulnerability in CISA's KEV catalog?
No. As of 2026-11-18, CISA's Known Exploited Vulnerabilities catalog (version 2026.11.13, 1,781 entries) lists no CODESYS CVE. As of the same date, the latest FIRST EPSS scores (dated 2026-11-17) are low: 0.029 for the 2020 web server overflow CVE-2020-10245, 0.020 for CVE-2022-47379 and 0.019 for CVE-2022-47391, with the 2024 to 2026 runtime CVEs below 0.01. CODESYS's own advisories for the Microsoft findings say no known public exploits specifically target them. Low scores do not make an exposed controller safe, because several runtime CVEs need no login.
Can SoftWSP tell me whether my CODESYS-based controllers are affected?
SoftWSP matches the components and versions it is given, or can identify in a firmware image, against NVD, CISA KEV, FIRST EPSS and CISA's ICS advisories, and AI writes a summary that cites the record behind each finding; an engineer reviews it before delivery. For a CODESYS-based PLC that means a component list with the device model, the vendor firmware version and, where known, the CODESYS runtime version. Which CODESYS fixes a vendor firmware contains, and whether user management, encryption and signing are enforced on the running controller, are decided in that engineer review against the vendor advisory.
Sources
- CODESYS GmbH Advisory 2023-02: Security update for CODESYS Control V3 (V3.0, 3 April 2023)
- CODESYS GmbH Advisory 2023-03: CVE-2022-47391 in CmpDevice
- Microsoft Security Blog: Multiple high severity vulnerabilities in CODESYS V3 SDK could lead to RCE or DoS (August 2023)
- Microsoft CoDe16 repository: white paper, runtime-version tool and Wireshark dissector
- CERT@VDE: CODESYS GmbH advisory list
- CERT@VDE VDE-2023-019: Multiple vulnerabilities in CmpApp, CmpAppBP and CmpAppForce
- CERT@VDE VDE-2023-025: Control runtime system memory and integrity check vulnerabilities
- CERT@VDE VDE-2023-066: OS command injection in multiple CODESYS Control products
- CERT@VDE VDE-2024-057: CODESYS web server vulnerable to DoS
- CERT@VDE VDE-2025-013: CODESYS (Edge) Gateway for Windows insecure default
- CERT@VDE VDE-2025-051: CODESYS Control V3 exposed PKI folder
- CERT@VDE VDE-2025-070: CODESYS Control V3 NULL pointer dereference
- CERT@VDE VDE-2026-011: CODESYS Control V3 untrusted boot application
- CERT@VDE VDE-2026-018: CODESYS Control V3 externally-controlled format string in Auditlog
- CERT@VDE VDE-2026-057: CODESYS Control out-of-bounds write in CmpWebServer
- CERT@VDE VDE-2026-097: CODESYS Control Runtime improper synchronization in monitoring
- CERT@VDE VDE-2023-026: WAGO products with vulnerabilities in e!Runtime / CODESYS V3 Runtime
- CISA ICSA-26-020-02: Schneider Electric devices using CODESYS Runtime (republication of SEVD-2023-192-04)
- CISA ICSA-24-030-07: Rockwell Automation LP30/40/50 and BM40 Operator Interface
- CISA ICSA-25-093-03: ABB ACS880 Drives Containing CODESYS RTS
- CISA ICSA-26-132-03: ABB AC500 V3 Multiple Vulnerabilities
- CISA ICSA-25-273-04: Festo Controller CECC-S, -LK, -D Family Firmware (Update A)
- CODESYS Online Help: Communication Settings (device editor)
- CODESYS Online Help: PLC Shell commands
- NVD: CVE-2022-47379
- NVD: CVE-2020-10245
- CISA Known Exploited Vulnerabilities catalog
- FIRST: Exploit Prediction Scoring System (EPSS)
About this guide
SoftWSP OT/ICS Desk
Covers the OT/ICS security cluster: 71 guides.

In this cluster
Questions about this page?
