Loading vulnerability…
CVE-2026-41551 is a path traversal vulnerability affecting ROS# in all versions prior to 2.2.2. According to the provided Siemens disclosure, the flaw exists because user-supplied input is not properly sanitized, allowing traversal outside of intended file paths. A remote attacker can exploit this weakness over the network to access arbitrary files on the affected device.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small proof-of-concept for CVE-2026-41551, a relative path traversal in Siemens ROS#/ros-sharp file_server/file_server2 before 2.2.2. The repo contains two files: a README documenting the vulnerability, affected versions, lab topology, and reproduction steps; and poc.py, a Python ROS2 client exploit. The exploit uses rclpy and the file_server2 GetBinaryFile service definition to connect to the ROS2 service endpoint /file_server/get_file, then submits a crafted package:// path with 12 ../ segments to escape the package share directory and read /etc/passwd from the remote victim. The code is straightforward and does not include post-exploitation, persistence, or arbitrary command execution; its sole capability is arbitrary file read via network-accessible ROS2 service abuse. The README makes clear that exploitation is cross-host over ROS2 DDS when the victim and attacker share a ROS_DOMAIN_ID and the victim is not restricted to localhost. Overall, this is a valid network-based file-read PoC demonstrating unauthenticated remote traversal against a vulnerable ROS2 file service.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.