CVE-2025-41658

A vendor fix is available.

• Fixedcodesys_psirt

  Update the following products to version 4.16.0.0. * 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 Raspberry Pi SL * CODESYS Control for WAGO Touch Panels 600 SL * CODESYS Virtual Control SL For the updated CODESYS Control SL products, CODESYS GmbH has implemented the necessary measures to address the identified security vulnerability. As a result, access to the runtime directories is now restricted to the Linux user account under which the CODESYS Control runtime is executed. Access is explicitly denied to all other non-administrator users. Note: Administrator users (e.g., root) may still retain access. The CODESYS Development System and the products available as CODESYS add-ons can be downloaded and installed directly with the CODESYS Installer or be downloaded from the CODESYS Store. Alternatively, as well as for all other products, you will find further information on obtaining the software update in the CODESYS Update area https://www.codesys.com/download/.

• FixedCODESYS Runtime Toolkitcodesys_psirt

  Version 3.5.21.20 of the following product provides an updated CODESYS Control V3 Runtime System Documentation: * CODESYS Runtime Toolkit In particular, Chapter 5 (Architecture Manual), Section 5.4 (Portings), Subsection 5.4.1 (Security Considerations), Subsection 5.4.1.1 (Operating System Folder Permissions) now provides detailed guidance for device manufacturers on how to address the described security vulnerability. The same information is also included as Mitigation in this advisory. CODESYS GmbH strongly recommends that this guidance be followed in order to effectively close the security vulnerability on affected devices. Devices are particularly at risk if they offer direct access to the operating system (e.g., via a local user interface or SSH) in combination with the presence or possibility of creating non-administrator user accounts for such access. Important: Updating the toolkit is not sufficient. For affected customer devices based on the CODESYS Runtime Toolkit the vulnerability needs to be resolved following the instructions in the mentioned documentation.

• FixedFirmware 3.1 installed on CR3171ifm_psirt

  will be fixed in Firmware Version 3.3

  https://www.ifm.com/de/en/product/CR3171#documents↗
• FixedFirmware 3.2 installed on CR3171ifm_psirt

  will be fixed in Firmware Version 3.3

  https://www.ifm.com/de/en/product/CR3171#documents↗
• MitigationCODESYS Runtime Toolkitcodesys_psirt

  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.

• MitigationFesto Automation Suite <2.8.0.138 installed with CODESYS Development System 3.0festo_psirt

  Starting from Festo Automation Suite version 2.8.0.138, Codesys is no longer bundled with the suite and must be downloaded and installed separately by the customer. To mitigate this vulnerability customers are advised to: Download the latest, patched version of Codesys directly from the official Codesys website. Follow the installation and update instructions provided by Codesys to ensure all security fixes are applied. Regularly monitor Codesys security advisories and apply updates promptly. Maintain the Festo Automation Suite connector up to date by installing FAS updates as released by Festo.

• MitigationFesto Automation Suite <2.8.0.138 installed with CODESYS Development System 3.5.16.10festo_psirt

  Starting from Festo Automation Suite version 2.8.0.138, Codesys is no longer bundled with the suite and must be downloaded and installed separately by the customer. To mitigate this vulnerability customers are advised to: Download the latest, patched version of Codesys directly from the official Codesys website. Follow the installation and update instructions provided by Codesys to ensure all security fixes are applied. Regularly monitor Codesys security advisories and apply updates promptly. Maintain the Festo Automation Suite connector up to date by installing FAS updates as released by Festo.

• MitigationFirmware 3.1 installed on CR3171ifm_psirt

  deactivate CodeSys enviroment on device

• MitigationFirmware 3.2 installed on CR3171ifm_psirt

  deactivate CodeSys enviroment on device

• MitigationFesto Automation Suite <2.8.0.138 installed with CODESYS Development System 3.0cisa_csaf_ot

  Starting from Festo Automation Suite version 2.8.0.138, Codesys is no longer bundled with the suite and must be downloaded and installed separately by the customer. To mitigate this vulnerability customers are advised to: Download the latest, patched version of Codesys directly from the official Codesys website. Follow the installation and update instructions provided by Codesys to ensure all security fixes are applied. Regularly monitor Codesys security advisories and apply updates promptly. Maintain the Festo Automation Suite connector up to date by installing FAS updates as released by Festo.

• MitigationFesto Automation Suite <2.8.0.138 installed with CODESYS Development System 3.5.16.10cisa_csaf_ot

  Starting from Festo Automation Suite version 2.8.0.138, Codesys is no longer bundled with the suite and must be downloaded and installed separately by the customer. To mitigate this vulnerability customers are advised to: Download the latest, patched version of Codesys directly from the official Codesys website. Follow the installation and update instructions provided by Codesys to ensure all security fixes are applied. Regularly monitor Codesys security advisories and apply updates promptly. Maintain the Festo Automation Suite connector up to date by installing FAS updates as released by Festo.

• No fix availableCODESYS Control for PLCnext SLcodesys_psirt

  For the following product no fix is available. * CODESYS Control for PLCnext SL Since there is no fix available for this product, CODESYS GmbH strongly recommends removing all other existing non-administrator users of the operating system and preventing their re-creation in order to neutralize the security vulnerability.