Siemens fixes code injection flaw in ROS# with version 2.3.1
Siemens has fixed a code injection vulnerability in ROS# that stems from how message definition files are handled, and the fix ships in version 2.3.1. Teams using ROS# in industrial projects are concerned, particularly in the critical manufacturing sector.
What to do now
- Product
- Siemens ROS#
- Affected versions
- ROS# versions before 2.3.1
- Fixed in
- ROS# 2.3.1 or later
- CVE
- CVE-2026-109097
CISA has republished a Siemens advisory covering ROS#, one of the vendor's software libraries. All versions before 2.3.1 contain a code injection vulnerability, tracked as CVE-2026-109097 and classified as CWE-94.
The flaw lies in how ROS# escapes the text of message definition files, which it does not do properly. An attacker who gets a victim to use a crafted definition file can inject arbitrary code into the program that ROS# generates from that file.
The attack is not direct. The user has to process a file supplied by a malicious party. The advisory does not report any active exploitation.
Siemens has released version 2.3.1 to address the issue and recommends upgrading to that release or a later one. According to the advisory, ROS# is deployed worldwide, mainly in the critical manufacturing sector. Siemens ProductCERT reported the vulnerability to CISA.
Siemens also repeats its general guidance: protect network access to devices and configure the environment according to its operational guidelines for industrial security.
What to do now
- Upgrade ROS# to version 2.3.1 or later on every development and code-generation workstation.
- Until the upgrade is in place, use only message definition files from trusted sources with ROS#.
- Review recently generated code built from externally sourced definition files for unexpected additions.
- As general good practice, follow Siemens' industrial security guidelines and restrict network access to affected equipment.