Skip to content

Vulnerabilities & Patches

CISA republishes Siemens ROS# advisory on code injection flaw

CISA says an attacker who submits a crafted message definition file can inject unauthorized code into the resulting program.

https://breach-signal.com/vulnerabilities/cisa-republishes-siemens-ros-code-injection-flaw/

Share

CISA republished Siemens ProductCERT’s advisory on a ROS# code injection flaw, converted from the vendor CSAF advisory SSA-435267, with an initial release date of Nov. 10, 2026. Critical Manufacturing is the critical infrastructure sector the advisory identifies as affected. CISA says an attacker who submits a crafted message definition file may inject unauthorized code into the program it produces.

According to CISA, ROS# has worldwide deployment, and Siemens has its headquarters in Germany. Siemens ProductCERT reported the vulnerability to CISA. Siemens released version 2.3.1 of ROS# and urges customers to update to the latest release.

Siemens says to protect network access to devices and to configure environments in line with its operational guidelines for Industrial Security. Customers should follow the recommendations found in the product manuals for the affected devices, Siemens also says. The company offers further Industrial Security information at siemens.com/industrialsecurity, and Siemens ProductCERT handles product security questions at siemens.com/cert/advisories.

CISA says organizations should limit network exposure, so control system devices are not reachable from the internet. It advises that control system networks sit behind firewalls and stay isolated from business networks. For required remote access, CISA recommends VPNs, while warning they can have vulnerabilities and need updates.

Organizations should complete an impact analysis and risk assessment before putting defensive measures in place, and should use recommended cybersecurity strategies to defend control system assets proactively, CISA also says. CISA says technical information paper ICS-TIP-12-146-01B, posted on cisa.gov/ics, contains more mitigation guidance. If an organization spots suspected malicious activity, it should send results to CISA, so the agency can track and correlate incidents.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *