CISA Details ROS# Message-Definition Code Injection Fixed in 2.3.1

P1 — VALIDATE AND UPDATEHigh · 8.2 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Update ROS# to 2.3.1 or later before processing untrusted message definitions, and review programs generated from questionable inputs.

Confirm Scope And Apply The Supported Remediation

What to do now: Record ROS# versions, generation pipelines, definition-file sources, build accounts and deployed programs derived from those files. The attacker must supply a crafted message-definition file that a user processes. This advisory does not describe arbitrary unauthenticated access to a running robot. Upgrade the generation toolchain to 2.3.1 or later and rebuild affected artifacts as appropriate. Restrict inputs to reviewed sources and keep build privileges limited. Generate representative messages and inspect output escaping in a controlled test. Retain source provenance, generator versions, reviewed diffs and signed or hashed build artifacts.

Open the authoritative advisory

Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeSiemens ROS# message generation
AdvisoryICSA-26-321-06
CVECVE-2026-109097
Authoritative release date2026-11-17T12:00:00Z — CISA release timestamp in the advisory page.
Authority revision dateNo separate material revision is confirmed for this CISA release.
Affected versionsROS# versions before 2.3.1.
Fixed versionROS# 2.3.1 or later
CVSS base score8.2 (CVSS v3.1)
CVSS severityHigh
Exploitation statusThe cited CISA ICS advisory does not confirm exploitation of these products in the wild.; no exploitation claim is inferred.

What Changed

CISA describes insufficient escaping of message-definition text that can place attacker-controlled code into a generated program.

What To Validate Now

  1. Inventory. Record ROS# versions, generation pipelines, definition-file sources, build accounts and deployed programs derived from those files.
  2. Establish applicability. The attacker must supply a crafted message-definition file that a user processes. This advisory does not describe arbitrary unauthenticated access to a running robot.
  3. Remediate. Upgrade the generation toolchain to 2.3.1 or later and rebuild affected artifacts as appropriate. Restrict inputs to reviewed sources and keep build privileges limited.
  4. Validate. Generate representative messages and inspect output escaping in a controlled test. Retain source provenance, generator versions, reviewed diffs and signed or hashed build artifacts.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Updating a generator does not change code already generated or deployed. Validate downstream robotics and industrial integrations before rollout.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.