CVE-2026-8153: Universal Robots Cobots Vulnerable to Unauthenticated RCE

An OS command injection vulnerability in the PolyScope 5 Dashboard Server enables unauthenticated remote code execution on Universal Robots industrial cobot co…

CVE-2026-8153: Universal Robots Cobots Vulnerable to Unauthenticated RCE

Universal Robots has officially released patch 5.25.1 for its PolyScope 5 software following the discovery of a critical OS command injection vulnerability. The technical flaw allows for unauthenticated remote code execution (RCE) on industrial cobot controllers, exposing systems to total compromise. The alert, issued in May 2026, saw both the vendor and CISA converge on the maximum risk severity, resulting in a CVSS score of 9.8.

The issue is not merely a coding error but is amplified by the typical network configurations in which these devices operate. According to technical analysis, the vulnerability allows an attacker with network access to bypass all forms of authentication, acting directly on the machine's operational core. This scenario raises immediate concerns regarding the integrity of production processes and the safety of operators interacting with collaborative robotics.

Key Takeaways
  • CVE-2026-8153 is an OS command injection vulnerability in the PolyScope 5 Dashboard Server with a critical CVSS severity score of 9.8.
  • An unauthenticated attacker with network access can execute commands on the controller's Linux operating system, compromising both confidentiality and integrity.
  • Vera Mens, a researcher at Claroty, identified that a lack of segmentation in OT networks can turn a single access point into a risk for an entire fleet.
  • Universal Robots has released version 5.25.1 as a definitive mitigation and recommends an immediate update for all vulnerable systems.

Technical Mechanisms of CVE-2026-8153

The core of the technical issue resides in the Dashboard Server, an integrated service within the PolyScope 5 software used for robot management and configuration. The OS command injection vulnerability occurs when the system fails to properly neutralize user-supplied input before passing it to the underlying operating system. This structural flaw allows a malicious actor to send manipulated command strings that are interpreted as legitimate instructions by the robot controller.

The official advisory from Universal Robots, as cited by SecurityWeek, clarifies the scope of the flaw: an attacker with access to the Dashboard Server port can "craft commands that are executed on the robot's operating system." The result is remote code execution that leads to a controller compromise. Since the controller operates on a Linux base, the attacker gains privileges that allow for the manipulation of the robotic arm's operational parameters and connected peripherals.

The critical severity (9.8) stems from the fact that the exploit requires neither access privileges nor user interaction. If the service port is reachable via the network, the system is vulnerable. In an industrial context, this means the boundary between digital commands and mechanical action is effectively removed, leaving the robot's logic at the mercy of unauthorized external instructions sent via simple network packets.

The Impact of Non-Segmented OT Networks

While Universal Robots specifies that cobots are not designed for direct internet exposure, the operational reality of modern factories presents an expanded attack surface. Vera Mens, a researcher at Claroty, emphasized that companies use the robots' Ethernet ports for critical purposes: data collection for central units, remote control, and integration with legacy industrial protocols such as MODBUS and EtherNet/IP to manipulate other OT equipment.

The primary risk is driven by network topology. Mens observed that operational technology (OT) networks are often "flat," meaning they lack robust internal segmentation. In this scenario, if an attacker successfully penetrates the corporate perimeter—perhaps through an office computer or a less secure IoT device—they can move laterally without obstacles until they reach the robot controllers, exploiting CVE-2026-8153 on a massive scale.

The use of protocols like MODBUS TCP, which by design lack encryption or strong authentication mechanisms, aggravates the situation. When these protocols coexist on non-segmented networks with devices vulnerable to RCE, the compromise of a single cobot can quickly escalate into control over an entire fleet. The ease with which this vulnerability can be exploited makes internal network perimeter protection as vital as the patch itself.

"The least severe outcome is the complete control of a single cobot (which can lead to hazards to humans), but the impact can extend to the compromise of an entire fleet of cobots and their peripherals" — Vera Mens, Claroty

Physical Risk and Operator Safety

In a collaborative robotics environment, the distinction between cybersecurity and physical safety becomes purely theoretical. Vera Mens explicitly warned that complete control of a robot can translate into "hazards to humans." Because cobots operate in close proximity to human personnel, any sudden or malicious alteration of their movement logic represents an immediate threat to workplace safety.

Gaining control of the controller via RCE allows an attacker to ignore or redefine software safety thresholds established during programming. Without the need for physical access to the teach pendant or configuration terminal, a malicious actor can modify work cycles, influencing not only production quality but also creating mechanical instability that standard production line monitoring systems may not predict.

Beyond the risk to physical safety, the impact on operational continuity is profound. The fleet compromise mentioned by Claroty suggests the possibility of coordinated sabotage attacks, where multiple robotic units are halted or altered simultaneously. In this context, recovery requires not only software remediation but also a physical audit of every unit to ensure mechanical parameters and calibrations have not been permanently tampered with.

Mitigation and Response

Organizations utilizing Universal Robots technology should treat the mitigation of this vulnerability as a top priority for operational resilience. It is recommended to follow a defense-in-depth strategy based on the technical data available in the vendor advisory and industry analyses.

Update to PolyScope 5.25.1. This is the only definitive measure to close the OS command injection flaw. The patch should be applied to all compatible controllers, prioritizing those managing critical processes or located in network segments with higher visibility. The update process must be verified to ensure the vulnerability in the Dashboard Server has been effectively neutralized.

Isolate the Dashboard Server port via segmentation. It is essential to map the network visibility of the Ethernet port used for the Dashboard Server. Access to this service should be restricted exclusively to authorized IP addresses and protected network segments (dedicated VLANs), preventing any device on the general corporate network from sending commands to the robot controller.

Monitor MODBUS and EtherNet/IP protocol usage. Given that these protocols are often the vectors through which robots interact with the rest of the plant, traffic monitoring is necessary to detect anomalies. If remote control or network manipulation is required, these functions should be secured behind gateways that require authentication, eliminating the implicit trust model typical of flat OT networks.

Review physical safety procedures. While awaiting the application of the patch, it is prudent to increase vigilance in areas where cobots operate in collaborative mode. Constant verification of motion program integrity and the use of hardware-based emergency stop systems—independent of the PolyScope software—are necessary precautionary measures to mitigate the risk of accidents caused by potential exploitation.

The Lesson of Network Topology

The case of CVE-2026-8153 demonstrates that a vulnerability in a single software component can have systemic repercussions when placed within an unprotected network architecture. Industrial robotics can no longer be considered an island isolated from the cyber world; the integration required for Industry 4.0 brings with it threats typical of general-purpose systems, such as OS command injections.

The lesson for OT security managers is clear: software patching is an essential step, but true defense lies in the ability to segment and monitor internal data flows. A patched robot placed in a flat network remains exposed to future zero-day risks. Only through conscious network design and the segmentation of critical domains is it possible to ensure that a coding error does not transform into a hazard for human life.

Information has been verified against cited sources and is current as of the time of publication.

Sources