Siemens Patches ROS# Code Injection Flaw

Siemens has released ROS# version 2.3.1 to fix a high-severity vulnerability that lets crafted message definition files inject arbitrary code.

Updated on Nov. 17, 2026 in Cybersecurity

Isometric editorial illustration of a bare white industrial robotic arm with a tangled teal cable bundle on a grey floor, evoking industrial software vulnerability.
Siemens released ROS# version 2.3.1 to patch CVE-2026-109097, a high-severity flaw that lets crafted message definition files inject arbitrary code into generated programs. AI Illustration. Upload story photo >

Siemens released ROS# version 2.3.1 to fix code injection vulnerability CVE-2026-109097 in earlier versions. Affected systems do not properly escape text in message definition files, so an attacker who can pass a crafted file to a user can inject arbitrary code into the generated program.

Why it matters

The affected product is classified as Critical Manufacturing sector infrastructure and is deployed worldwide, so organizations that rely on ROS# face exposure until they update. The vulnerability was reported to CISA by Siemens ProductCERT, and CISA's republication keeps the advisory in circulation for operators.

The vulnerability, CVE-2026-109097, carries a CVSS v3.1 base score of 8.2, rated HIGH, and is fixed in ROS# version 2.3.1, which is the first release to properly escape message definition file text. Whether any attacks have been observed in the wild is not addressed in the advisory.

The players

Siemens

Siemens is a German industrial conglomerate whose ProductCERT team handles coordinated disclosure of security vulnerabilities in its products.

CISA

The U.S. Cybersecurity and Infrastructure Security Agency is the federal body that coordinates vulnerability disclosure and republishes vendor advisories for critical infrastructure operators.

The details

The flaw stems from affected systems failing to properly escape text of message definition files, which allows a crafted file to inject arbitrary code that the generated program then executes. Siemens ProductCERT reported the vulnerability to CISA, and the vendor's remedy is to update ROS# to version 2.3.1 or later.

Timeline

  1. Siemens initially released advisory SSA-435267 on November 10, 2026.

  2. CISA republished the Siemens advisory as revision 2 on November 17, 2026.

Tech Race

The advisory fits a pattern in which industrial software vendors such as Siemens disclose flaws through ProductCERT, and CISA then republishes them to reach operators of critical manufacturing systems. The episode shows how vendor-led disclosure and federal re-publication work together in the industrial control software market.

Organizations running ROS# should update to version 2.3.1 or later to close the code injection path. Engineers who generate programs from message definition files should treat any externally supplied file as untrusted until the update is applied.

The takeaway

Teams using ROS# should prioritize moving to version 2.3.1 and should validate any message definition file before it is used to generate code. Routine vetting of inputs to code generators can limit the reach of flaws like this one.

Further reading

Explore more Cybersecurity coverage for context on how vendors and agencies handle software flaws.

More information

Review the Siemens ProductCERT security advisories for the full technical notice and patch details.

Source note: This article includes information reported by IT Security News - cybersecurity, infosecurity news.