# CVE-2026-41551: Path traversal in ROS#

> A remote attacker can access arbitrary files on the device due to improper input sanitization in the ROS# library.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-gmpj-93q6-2282

## What is CVE-2026-41551?

CVE-2026-41551 is a critical path traversal vulnerability in Siemens ROS#, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in ROS# (All versions < V2.2.2). Affected versions contain a path traversal vulnerability because user input is not properly sanitized.
This could allow a remote attacker to access arbitrary files on the device.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-41551?


## How do I fix CVE-2026-41551?

No fix has been published for CVE-2026-41551 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41551 being exploited?

There is no known exploitation of CVE-2026-41551 in the wild and no public exploit code.

Public exploit code:

- ROS# 路径遍历漏洞(CVE-2026-41551) (github_poc): https://github.com/selecthch/CVE-2026-41551

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41551 and fix it if it is affected.

What it is: CVE-2026-41551 is a critical path traversal vulnerability in Siemens ROS#, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41551 in the wild and no public exploit code.

Affected product: Siemens ROS#. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41551/ (Markdown: https://insights.sbomify.com/CVE-2026-41551/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41551
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41551
- OSV: https://osv.dev/vulnerability/CVE-2026-41551

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41551/
Summaries are generated and may contain mistakes; the official description above is the record.