CVE-2026-109097: ROS# code injection in code generator

Q: Is CVE-2026-109097 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Q: What does this mean?

ROS# contains a code injection flaw that lets an attacker inject arbitrary code into the program it generates. The advisory describes this as a code injection vulnerability in ROS# before 2.3.1.

Q: Am I affected, and how do I check?

All versions of ROS# below V2.3.1 are affected. To check a setup, look up the ROS# version in use and compare it with V2.3.1; any version earlier than that falls in the affected range.

Q: How do I fix CVE-2026-109097?

Update ROS# to V2.3.1 or later, which is the fixed version named in the advisory.

Summary

Affected software is ROS#, and the bug can only be reached locally, by an attacker with low-privilege access who must get a user to take an action, such as opening a crafted message definition file. Successful exploitation could let the attacker inject arbitrary code into the program generated from that file.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

A vulnerability has been identified in ROS# (All versions < V2.3.1). Affected systems do not properly escape text of message definition files. This could allow an attacker that is able to pass a crafted message definition file to the user to inject arbitrary code into the generated program.

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure5/25Specific setups only
Reach?/20Unknown. No tracked technology or package matched
Severity8.2/10CVSS 8.2
No patch0/5No signal

What would change the score

Would score about 63 if added to CISA KEV
Would score about 58 if CISA's SSVC rates exploitation active
Would score about 23 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

Check whether your setup matches what the bug needs.
ROS# version before 2.3.1 (all versions below V2.3.1 are affected)
Upgrade to a fixed version: V2.3.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-109097 (A vulnerability has been identified in ROS# (All versions < V2.3.1).), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-109097 (entry last updated 2026-11-10):
Affected:
- Siemens ROS#: fixed in V2.3.1
Fixed versions: V2.3.1.
Conditions (all must be true for the bug to be hit):
- ROS# version before 2.3.1 (all versions below V2.3.1 are affected) (source: https://cert-portal.siemens.com/productcert/html/ssa-435267.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, a user action.
CISA KEV: CVE-2026-109097 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-109097 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert-portal.siemens.com/productcert/html/ssa-435267.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Entry: https://cve.now/CVE-2026-109097
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-109097.

Timeline

Nov 10, 2026, 11:30 AM UTCCVE published
Nov 10, 2026, 11:43 AM UTCFirst seen by cve.now

Affected versions

Siemens ROS#
fixed in V2.3.1

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Link
cert-portal.siemens.com · productcert/html/ssa-435267.html

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-109097
Record
NVD · CVE-2026-109097

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-109097

Is CVE-2026-109097 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

ROS# contains a code injection flaw that lets an attacker inject arbitrary code into the program it generates. The advisory describes this as a code injection vulnerability in ROS# before 2.3.1.Source: cert-portal.siemens.com

Which versions are affected by CVE-2026-109097?

ROS#: before V2.3.1.Source: cve.now feed data

Am I affected, and how do I check?

All versions of ROS# below V2.3.1 are affected. To check a setup, look up the ROS# version in use and compare it with V2.3.1; any version earlier than that falls in the affected range.Source: cert-portal.siemens.com

How do I fix CVE-2026-109097?

Update ROS# to V2.3.1 or later, which is the fixed version named in the advisory.Source: cert-portal.siemens.com

A vulnerability has been identified in ROS# (All versions < V2.3.1).