CISA + vendors
ICS Advisories
Advisories specifically aimed at industrial control systems — from CISA ICS-CERT and directly from vendors (including Siemens, ABB, Schneider Electric, WAGO and Phoenix Contact) — including revision history (initial publication, Update A, Update B) and linked CVEs.
499
Found
Advisory data: live connection— last retrieved: 20 November 2026 at 22:19.
Filters
499 advisories found
Advisory2025-06_VDE-2025-049
CODESYS Control V3 - Insecure default permissions
Risk evaluation
On certain operating systems (e.g., Linux), default file system permissions may allow read access to the files of the CODESYS Control runtime system for non-administrator users. The documentation provided with the CODESYS Runtime Toolkit does not explicitly address this risk. As a result, products based on the toolkit may unintentionally expose sensitive runtime files to local operating system users with limited privileges. CODESYS Control runtime system based devices are affected if they provide access to the operating system (e.g., via a local user interface or SSH) and user accounts without administrator rights for this access exist or can be created.
Mitigation summary
If the CODESYS Control runtime system is operated on an operating system with multi-user support, other users may potentially gain access to runtime-related files. Thus, it is essential to configure the storage locations for CODESYS Control runtime files in accordance with the operating system's security best practices. These locations should, by default, restrict access to unauthorized users. If the operating system does not support such access control mechanisms or if implementing them is not feasible, an alternative approach is to explicitly revoke read and write permissions for all non-administrative users on the directories used by the CODESYS Control runtime system. The following directories must be secured: * The directory containing configuration files * The directory containing binary files * The working directory used by the runtime system Note: Protecting individual files is not sufficient. The entire directories must be secured to ensure that any files created in the future are also protected. Alternatively, where applicable, all non-administrative user accounts can be removed from the system, and their re-creation should be prevented. Additionally, it is recommended to disable remote access methods that allow file access (e.g., SSH) wherever possible, in order to reduce the overall attack surface. Best practice recommendations for Linux and QNX Systems: * Create a dedicated privileged group for accessing the above-mentioned directories, and add the user account under which the runtime process is executed to this group. * Set the file system permissions for these directories to deny access to "other" users (e.g., chmod o-rx). * If access for additional users is required, they can be added to the privileged group as needed.
Revision history (1)
Initial publication — 4 August 2025
Initial revision.
Risk evaluation
An authenticated remote attacker can exploit an undocumented method to escape the LUA sandbox in mbNET devices, enabling the execution of arbitrary operating system commands and leading to full system compromise.
Mitigation summary
Update mbNET/mbNET.rokey to at least version 7.3.0\ **Note**: mbNET HW1 is EOL and will not receive any further updates.
Revision history (1)
Initial publication — 31 July 2025
Initial revision.
Risk evaluation
An authenticated remote attacker can exploit an undocumented method to escape the LUA sandbox in REX200/250 devices, enabling the execution of arbitrary operating system commands and leading to full system compromise.
Mitigation summary
Update REX 200/250 to at least version 7.3.0\ **Note**: REX 300 is EOL and will not receive any further updates.
Revision history (1)
Initial publication — 31 July 2025
Initial revision.
FSA-202207
Festo: CPX-CEC-C1 and CPX-CMXX, Missing Authentication for Critical Webpage Function
Risk evaluation
Unauthenticated access to critical webpage functions (e.g. reboot) may cause a denial of service of the device.
Mitigation summary
Currently no fix is planned. Festo recommends limiting access to the webserver (tcp port 80) of the device to what is absolutely necessary. Replace CPX-CEC-C1 with follow-up product CPX-CEC-C1-V3. Replace CPX-CMXX with follow up product CPX-CEC-M1-V3.
Revision history (4)
Initial publication — 20 September 2022
Initial revision.
Update A — 19 October 2022
Added Control block-Set CPX-CEC-C1 and Control block-SET CPX-CMXX to affected products.
Update B — 11 January 2024
Adjust link to VDE Advisory
Update C — 28 July 2025
Adjusted to VDE template. Change title from 'CPX-CEC-C1 and CPX-CMXX, Missing Authentication for Critical Webpage Function' to 'Festo: CPX-CEC-C1 and CPX-CMXX, Missing Authentication for Critical Webpage Function'. Updated legal disclaimer to add references to special provisions. Remediations were consolidated into one.
VDE-2025-052
Weidmueller: Security routers IE-SR-2TX are affected by multiple vulnerabilities
Published
11 June 2025
Last update
23 July 2025
Affected sectors
Risk evaluation
Weidmueller security routers IE-SR-2TX are affected by multiple vulnerabilities (CVE-2025-41661, CVE-2025-41663, CVE-2025-41683, CVE-2025-41684, CVE-2025-41687). Weidmueller has released new firmware versions of the affected products to fix the vulnerabilities. **Update Version 1.1.0:** Added CVEs CVE-2025-41683, CVE-2025-41684 and CVE-2025-41687. Updated CVSS Score for CVE-2025-41663. Removed CVE-2025-41662.
Mitigation summary
Update to version V1.49
Revision history (2)
Initial publication — 11 June 2025
Initial version
Update A — 23 July 2025
Added CVEs CVE-2025-41683, CVE-2025-41684 and CVE-2025-41687. Updated CVSS Score for CVE-2025-41663. Removed CVE-2025-41662.
Published
21 July 2025
Last update
21 July 2025
Linked CVEs
Affected sectors
Risk evaluation
Multiple vulnerabilities in all mbNET.mini devices with firmware <= 2.3.2 that allow an attacker to gain full control over the device.
Mitigation summary
As this is an authenticated exploit, you can mitigate it by making sure that no malicious actor can login to a vulnerable device.
Revision history (1)
Initial publication — 21 July 2025
Initial revision.
Published
21 July 2025
Last update
21 July 2025
Linked CVEs
Affected sectors
Risk evaluation
Multiple vulnerabilities in all REX 100 devices with firmware <= 2.3.2 that allow an attacker to gain full control over the device.
Mitigation summary
As this is an authenticated exploit, you can mitigate it by making sure that no malicious actor can login to a vulnerable device.
Revision history (1)
Initial publication — 21 July 2025
Initial revision.
FSA-202203
Festo: Controller CECC-S,LK,D family firmware 2.4.2.0 - multiple vulnerabilities in CODESYS V3 runtime system
Published
18 July 2022
Last update
10 July 2025
Linked CVEs
Affected sectors
Energieopwekking
Risk evaluation
The Festo controller CECC product family in firmware version 2.4.2.0 is affected by multiple vulnerabilities in the CODESYS V3 runtime.
Mitigation summary
No fix planned. This issue will be handled with next hardware generation release.
Revision history (3)
Initial publication — 18 July 2022
Initial version.
Update A — 11 January 2024
Adjust link to VDE Advisory, TLP and update some CVE information, where CVSS was not known before.
Update B — 10 July 2025
Adjusted to VDE template. Changed document title from 'Festo Controller CECC-S,-LK,-D Family Firmware = 2.4.2.0 - Multiple Vulnerabilities in CODESYS V3 Runtime System' to' Festo: Controller CECC-S,LK,D family firmware 2.4.2.0 - multiple vulnerabilities in CODESYS V3 runtime system'. Updated legal disclaimer to add references to special provisions.
Risk evaluation
During installation, identical certificates are installed across all systems instead of unique ones, which are intended for JWT Token encryption and signing.
Mitigation summary
Update to WAGO Device Sphere version 1.0.1. WAGO Device Sphere version 1.0 can't be used after the 30.06.2025.
Revision history (2)
Initial publication — 12 June 2025
Initial release.
Update A — 7 July 2025
fixed typo in CVE-ID
Risk evaluation
Authentication is not configured by default for the Node-RED server on the Pilz industrial PC IndustrialPI. An unauthenticated remote attacker has full access to the Node-RED server and can run arbitrary operating system commands on the underlying operating system with privileged rights.
Mitigation summary
Consult our PDF with remediations which you can find under [www.pilz.com/downloads](https://www.pilz.com/search#currentPage=1&SEARCH=Security%20Advis.%20IndustrialPI%20Remediat.). In order to activate the authentication as described in the PDF, you have to have the Node-RED service enabled via the web application.
Revision history (1)
Initial publication — 1 July 2025
Initial Version
Risk evaluation
The Pilz industrial PC IndustrialPI webstatus application is vulnerable to an authentication bypass.
Mitigation summary
Update the webstatus package to version 2.4.6 via the 'apt' package manager. Use 'sudo apt update && sudo apt upgrade -y' to pull and install all available updates for the IndustrialPI. To check the version of the webstatus package, use 'dpkg -l | grep revpi-webstatus'.
Revision history (1)
Initial publication — 1 July 2025
Initial Version
Published
30 June 2025
Last update
30 June 2025
Linked CVEs
Affected sectors
Risk evaluation
PiCtory, a web application to configure the Pilz industrial PC IndustrialPI, has three vulnerabilities with varying degrees of severity. The first two are of critical severity and can lead to a bypass of authentication and a cross-site-scripting attack. The third vulnerability with medium severity puts PiCtory at a risk of a reflected cross-site-scripting attack.
Mitigation summary
Update the PiCtory package to version 2.12 via the 'apt' package manager. Use 'sudo apt update && sudo apt upgrade -y' to pull and install all available updates for the IndustrialPI. To check the version of the pictory package, use 'dpkg -l | grep pictory'.
Revision history (1)
Initial publication — 30 June 2025
Initial Version
VDE-2025-043
Lenze: PLC Designer V4 with insecure storage of sensitive information
Risk evaluation
A security vulnerability was discovered in the PLC Designer V4 in the version 4.0.0 where the programmer of a Controller can set a password for the connected device. Here it is possible in an interface of the PLC Designer V4 for the programmer to enter a password for the Device. There is a special constellation where the password entered appears in plain text. Only the display in the tool is affected and not the management of the password on the device. This vulnerability of PLC Designer V4 only occurs in combination with the devices c430 controller, c520 controller and c550 controller and not in combination with other devices, as this functionality is only used here. It is generally recommended that all users update to 4.0.1, but especially all users who operate PLC Designer V4 in combination with the controllers mentioned.
Mitigation summary
This vulnerability has been fixed in the new version. All users are strongly recommended to use the new version 4.0.1.
Revision history (1)
Initial publication — 25 June 2025
Initial Version
Risk evaluation
Two vulnerabilities in mbCONNECT24/mymbCONNECT24 can lead to user enumeration an password bypass.
Mitigation summary
Update to latest version: 2.16.5
Revision history (1)
Initial publication — 24 June 2025
Initial revision.
Risk evaluation
The mb24api endpoint reachable when connected via VPN is missing authentication for sensitive functions. This can lead to information disclosure of user- and device names and to DoS.
Mitigation summary
Update to latest version: 2.18.0
Revision history (1)
Initial publication — 24 June 2025
Initial revision.
Risk evaluation
Two vulnerabilities in myREX24/myREX24.virtual can lead to user enumeration an password bypass.
Mitigation summary
Update to latest version: 2.16.5
Revision history (1)
Initial publication — 24 June 2025
Initial revision.
Risk evaluation
The mb24api endpoint reachable when connected via VPN is missing authentication for sensitive functions. This can lead to information disclosure of user- and device names and to DoS.
Mitigation summary
Update to latest version: 2.18.0
Revision history (1)
Initial publication — 24 June 2025
Initial revision.
Published
6 July 2022
Last update
23 June 2025
Affected sectors
Risk evaluation
The Festo controller CECC-X-M1 product family in multiple versions are affected by a preauthentication command injection vulnerability. Update A, 2022-07-05 Remediation has been updated. Fixed firmwares are now available.
Mitigation summary
Please update to firmware versions as described below: | Product | Product Details | Fixed in version | |-----------------------------|-----------------------------------------------------------|------------------| | Controller CECC-X-M1 | Festo:Partnumber:4407603 Festo:Ordercode:CECC-X-M1 | 3.8.18 | | Controller CECC-X-M1 | Festo:Partnumber:8124922 Festo:Ordercode:CECC-X-M1 | 4.0.18 | | Controller CECC-X-M1-MV | Festo:Partnumber:4407605 Festo:Ordercode:CECC-X-M1-MV | 3.8.18 | | Controller CECC-X-M1-MV | Festo:Partnumber:8124923 Festo:Ordercode:CECC-X-M1-MV | 4.0.18 | | Controller CECC-X-M1-MVS1 | Festo:Partnumber:4407606 Festo:Ordercode:CECC-X-M1-MV-S1 | 3.8.18 | | Controller CECC-X-M1-MVS1 | Festo:Partnumber:8124924 Festo:Ordercode:CECC-X-M1-MV-S1 | 4.0.18 | | Controller CECC-X-M1-YYJKP | Festo:Partnumber:4803891 Festo:Ordercode:CECC-X-M1-YYJKP | 3.8.18 | | Controller CECC-X-M1-YSL1 | Festo:Partnumber:8082793 Festo:Ordercode:CECC-X-M1-YS-L1 | 3.8.18 | | Controller CECC-X-M1-YSL2 | Festo:Partnumber:8082794 Festo:Ordercode:CECC-X-M1-YS-L2 | 3.8.18 | | Servo Press Kit YJKP | Festo:Partnumber:8077950 Festo:Ordercode:YJKP | 3.8.18 | | Servo Press Kit YJKP | Festo:Partnumber:8058596 Festo:Ordercode:YJKP | 3.8.18 |
Revision history (3)
Initial publication — 6 July 2022
Initial revision.
Update A — 5 June 2025
Fix: quotation mark
Update B — 23 June 2025
Changed Document ID
Published
16 June 2025
Last update
16 June 2025
Linked CVEs
Affected sectors
Risk evaluation
The base ctrlX OS apps Device Admin and Solutions contain multiple vulnerabilities. In a worst case scenario, a remote authenticated (low-privileged) attacker might be able to execute arbitrary OS commands running with higher privileges.
Mitigation summary
Update to Solutions 2.6.1 which is available in the WAGO Download center.
Revision history (1)
Initial publication — 16 June 2025
Initial release.
VDE-2021-030
MB connect line: two vulnerabilities in mymbCONNECT24, mbCONNECT24 (Update A)
Published
7 September 2022
Last update
6 June 2025
Linked CVEs
Affected sectors
Risk evaluation
Two issues have been discovered in mymbCONNECT24 and mbCONNECT24 in all versionsincluding V2.8.0. Updated affected versions (and solution) due to incomplete fixes in previous versions
Mitigation summary
CVE-2021-34575: Update to 2.9.0 CVE-2021-34574: Update to 2.12.1
Revision history (3)
Initial publication — 7 September 2022
Initial revision.
Update A — 7 September 2022
Update A
Update B — 6 June 2025
Fixed CVE-IDs in Solution/Remidiation
Risk evaluation
Several WAGO Firmwares are vulnerable to a to a remote attack which allows to bypass the integrity check through OpenSSH. This called Terrapin attack occurs because of mishandled handshake phase.
Mitigation summary
A fix for the affected Firmwares will be provided with the following firmware versions: - FW22, Patch 2 installed on 750-810x - FW22, Patch 2 installed on 750-821x - FW22, Patch 2 installed on 762-4x0x - FW22, Patch 2 installed on 762-5x0x - FW22, Patch 2 installed on 762-6x0x - FW22, Patch 2 installed on 752-8303 - FW27 installed on 750-811x - FW27 installed on 750-821x - FW27 installed on 751-9301 - FW27 installed on 751-9401 - FW27 installed on 762-4x0x - FW27 installed on 762-5x0x - FW27 installed on 762-6x0x - FW27 installed on 752-8303 - Custom Firmware 03.03.08 (80) installed on 750-820x - Custom Firmware 04.03.03 (72) installed on 751-9301 - Custom Firmware 04.03.03 (72) installed on 751-9401 - Custom Firmware 04.04.03 (70) installed on 750-821x
Revision history (2)
Initial publication — 22 February 2024
Initial revision.
Update A — 5 June 2025
Fix: version space
Risk evaluation
Several Pilz software products do not properly check pathnames contained in archives. An attacker can utilise this vulnerability to write arbitrary files, potentially leading to code execution.
Mitigation summary
Please visit the Pilz Shop (www.pilz.com/en-INT/eshop) to check for the fixed version
Revision history (2)
Initial publication — 24 November 2022
Initial revision.
Update A — 5 June 2025
Fix: quotation mark
VDE-2022-003
BECKHOFF: Null Pointer Dereference vulnerability in products with OPC UA technology
Risk evaluation
By tricking clients of the mentioned products into contacting malicious OPC UA servers and thereby acting as OPC UA clients, a crash of the component can be provoked.
Mitigation summary
Have your applications configured to use other than SecurityMode=None for all OPC UA connections. Avoid that these connect to an unknown OPC UA server with SecurityMode=None. In particular, avoid that your applications connect to servers which they discover via mDNS, a Local Discovery Server (LDS), an untrusted Global Discovery Server (GDS) or even trusted GDS using SecurityMode=none. Especially in the latter case an adversary might be able to apply the 'man in the middle' pattern to attack the connection and inject a bad message which triggers the vulnerability.
Revision history (2)
Initial publication — 1 March 2022
Initial revision.
Update A — 5 June 2025
Fix: quotation mark
Risk evaluation
Under certain circumstances, opening a specially crafted 7-zip package can exploit an integer underflow vulnerability in 7-zip versions up to and including 22.x This vulnerability allows for a remote code execution, resulting in unauthorized (remote) access to, change of data or disruption of the whole service.
Mitigation summary
Please download the replacement tool. For additional questions please contact your TRUMPF Service with the PR number 501709.
Revision history (2)
Initial publication — 23 January 2024
Initial revision.
Update A — 5 June 2025
Fix: quotation mark
Risk evaluation
The Year 2038 Problem affects systems using a 32-bit integer to represent time as the number of seconds since January 1st, 1970. On January 19, 2038, at 03:14:07 UTC, the time value will exceed the maximum for a 32-bit integer, causing an overflow and resetting it to a negative number.
Mitigation summary
Due to the low impact of the vulnerability and the fact that only the logging functionality is affected, there is no fix planned.
Revision history (1)
Initial publication — 2 June 2025
Initial release.