Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionCVE.org
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.
AnalysisAI
Remote path traversal in Siemens ROS
versions prior to V2.2.2 enables unauthenticated attackers to read arbitrary files from affected systems due to insufficient input sanitization. The vulnerability affects the ROS
library, a C
.NET implementation for Robot Operating System communication, with CVSS 9.3 critical severity. No active exploitation or public exploit code has been identified at time of analysis, though the network-accessible attack vector and lack of authentication requirements present significant risk for robotics systems using this library.
Technical ContextAI
ROS
is Siemens' C
.NET library that enables communication between Robot Operating System (ROS) environments and Microsoft .NET applications, commonly used in industrial robotics and automation systems. The vulnerability stems from CWE-23 (Relative Path Traversal), where the application fails to properly neutralize special elements within pathname inputs such as '../' sequences. When user-supplied input containing directory traversal sequences is processed without adequate validation or sanitization, attackers can escape intended directory restrictions and access files outside the application's designated file system scope. The affected CPE (cpe:2.3:a:siemens:ros#) indicates this is a library-level vulnerability that could impact any application or robotic system integrating ROS
for ROS communication functionality. Path traversal vulnerabilities in robotics libraries are particularly concerning as they may expose configuration files, credentials, or operational data critical to industrial control systems.
RemediationAI
Upgrade Siemens ROS
to version V2.2.2 or later, as confirmed by Siemens ProductCERT advisory SSA-357982 (https://cert-portal.siemens.com/productcert/html/ssa-357982.html). This vendor-released patch addresses the input sanitization deficiency causing the path traversal vulnerability. Organizations should prioritize systems with ROS
instances accessible from untrusted networks or multi-tenant environments. If immediate patching is not feasible, implement network segmentation to restrict access to ROS
endpoints exclusively from trusted robotics control networks, blocking external and cross-segment access via firewall rules (trade-off: may limit legitimate remote monitoring capabilities). Deploy application-layer filtering or web application firewall rules to detect and block requests containing path traversal patterns such as '../', '..\', URL-encoded variants (%2e%2e%2f), and Unicode equivalents, though this provides only partial protection against sophisticated bypass techniques. Review file system permissions to ensure the ROS
process runs with least-privilege access, limiting the scope of files accessible even if traversal succeeds (trade-off: may require application reconfiguration and testing). Monitor file access logs for unusual patterns indicating traversal attempts, particularly access to configuration directories, credential stores, or system files outside expected ROS
operational paths.
An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3
Integer Overflow or Wraparound vulnerability in the XML RPC library of OpenRobotics ros_comm communications packages all
An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3
SROS 2 0.8.1 (after CVE-2019-19625 is mitigated) leaks ROS 2 node-related information regardless of the rtps_protection_
SROS 2 0.8.1 (which provides the tools that generate and distribute keys for Robot Operating System 2 and uses the under
An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3
An infinite loop in Open Robotics ros_comm XMLRPC server in ROS Melodic through 1.4.11 and ROS Noetic through1.15.11 all
Siemens RuggedCom Rugged Operating System (ROS) before 3.12, ROX I OS through 1.14.5, ROX II OS through 2.3.0, and Rugge
Same weakness CWE-23 – Relative Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-29434
GHSA-gmpj-93q6-2282