# SZB-4a756643b0: Siemens discloses code injection flaw CVE-2026-109097 in ROS# before 2.3.1

Siemens published an ICS advisory saying ROS# before version 2.3.1 has a code injection flaw (CVE-2026-109097, CVSS 8.2). Siemens ProductCERT reported the vulnerability to CISA, and Siemens has released version 2.3.1.

- Type: Early warning
- Kind: Pending CVE
- Vendor: Siemens
- Product: ROS#
- Status: Confirmed
- Sources: 1 distinct
- First seen: 2026-11-17 16:20 UTC
- Confirmed: 2026-11-17 16:20 UTC

Written by a model from the sources below. Verify against them.

## What to do

- Update ROS# to version 2.3.1 or later.
- Restrict network access to ROS# systems and follow Siemens' operational guidelines for industrial security.
- Only pass message definition files from trusted sources until the update is applied.

## Timeline

- 2026-11-17 12:00 UTC: Made public by CISA advisories
- 2026-11-17 16:20 UTC: First seen by cve.now
- 2026-11-17 16:20 UTC: Confirmed by CISA advisories

## Evidence (1 source)

- 2026-11-17 · Official · [CISA advisories](https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-06): “ROS# before version 2.3.1 contains a code injection vulnerability that 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.”

## Corrections

None so far.

Something wrong on this page? Report an error: https://github.com/sazabi/cve.now/issues/new?title=Wrong%20fact%20on%20SZB-4a756643b0&body=https%3A%2F%2Fcve.now%2FSZB-4a756643b0%0A%0AWhat%20is%20wrong%2C%20and%20the%20source%20that%20shows%20it%3A%0A

## Questions about SZB-4a756643b0

### Has Siemens confirmed it?

Yes. Confirmed by CISA advisories.

Source: https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-06

### What should Siemens and ROS# users do?

Update ROS# to version 2.3.1 or later. Restrict network access to ROS# systems and follow Siemens' operational guidelines for industrial security. Only pass message definition files from trusted sources until the update is applied.

### Does it have a CVE?

Yes. It is tracked as CVE-2026-109097.

Source: https://cve.now/CVE-2026-109097

## Tracked as

- [CVE-2026-109097](https://cve.now/CVE-2026-109097.md)

## Related

- Browse: [Early warnings](https://cve.now/early-warnings.md)

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/SZB-4a756643b0
Site guide for agents: https://cve.now/llms.txt
