Siemens ROS# code injection flaw fixed in 2.3.1
The exploit needs a crafted message definition file to reach a user, but patching is a straight version bump.
TL;DR
CISA republished a Siemens advisory for CVE-2026-109097, a code injection flaw in ROS# before version 2.3.1 rated CVSS 8.2 (HIGH). The affected systems don't properly escape text in message definition files, so an attacker who passes a crafted file to a user could inject arbitrary code into the generated program. Siemens recommends updating to V2.3.1 or later.
Siemens ProductCERT disclosed the flaw, and CISA republished it as a verbatim advisory. The vulnerability is CWE-94, improper control of code generation. Because the affected systems fail to escape text in message definition files, a crafted file that reaches a user can inject code into whatever program ROS# generates from it.
The vector matters for how operators read the risk. CISA's listing carries a CVSS 3.1 score of 8.2 with the string AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H. That's a local attack vector with user interaction required: an attacker has to get a crafted message definition file in front of someone who opens it. Once that happens, the impact is high across confidentiality, integrity, and availability, with scope change.
There's nothing subtle about the remediation. Siemens recommends updating to V2.3.1 or later, and there's no mitigation listed as a substitute. Organizations running ROS# in critical manufacturing environments should treat the version under 2.3.1 as known-affected and schedule the bump rather than hunting for a config change.
The full CVE details sit on CISA's advisory page, and Siemens directs technical follow-up to its ProductCERT. The republication note is explicit that this is a direct conversion of Siemens' CSAF advisory, published as-is for visibility.
Published ·Deep Fathom