CISA published ICS advisory ICSA-26-134-17 on 14 May 2026, flagging a critical OS command injection vulnerability in Universal Robots’ PolyScope 5 operating system for collaborative robots. The flaw — tracked as CVE-2026-8153 — carries a CVSS 3.1 base score of 9.8 and requires no authentication to exploit. Any attacker with network access to the robot controller can execute arbitrary commands on the underlying operating system.
Universal Robots has deployed more than 100,000 cobots across thousands of facilities in the United States, Mexico, Europe, and Asia-Pacific. The affected systems are found on automotive assembly lines, electronics manufacturing floors, pharmaceutical packaging operations, and warehouse fulfilment centres — environments where a compromised robot controller can halt production, alter safety-critical parameters, or provide a foothold into wider OT networks.
The Vulnerability
The flaw sits in PolyScope 5’s Dashboard Server, a management interface that listens by default on TCP port 29999. The Dashboard Server accepts user-supplied input and passes it to the underlying Linux-based operating system without sanitising special characters. This is a textbook CWE-78 (Improper Neutralisation of Special Elements in an OS Command) failure.
No credentials are required. An attacker who can reach port 29999 can craft a single malformed command string that breaks out of the intended input context and runs arbitrary shell commands with the privileges of the Dashboard Server process. From there, an attacker can:
- Modify robot programs, speed limits, force thresholds, and TCP payload configurations
- Disable safety monitoring functions — e-stops, collaborative speed reductions, force-limited operation modes
- Install persistent malware on the controller
- Use the controller as a pivot to enumerate and attack other OT assets on the same network segment
All PolyScope 5 versions prior to 5.25.1 are affected. PolyScope 3 (e-Series legacy) is not listed in the advisory and appears unaffected.
Exposure Context
The Dashboard Server is enabled by default on PolyScope 5 installations and is documented in Universal Robots’ own integration guides as the standard programmatic interface for third-party systems — SCADA integrations, MES connections, cell controllers, and remote monitoring dashboards. This means port 29999 is frequently open and reachable across the OT network, and in some misconfigured sites it is accessible from the IT network or directly from the internet.
Organisations that have integrated PolyScope controllers with enterprise systems via flat or inadequately segmented networks are at the highest risk. A single exploitable controller reachable from a business network gives an adversary a direct path into the production floor.
Remediation
Universal Robots released PolyScope 5.25.1 to address the vulnerability. The update applies via the standard PolyScope software update mechanism and does not require a robot hardware change.
Priority actions:
-
Patch immediately. Upgrade all PolyScope 5 installations to version 5.25.1 or later. Universal Robots’ firmware update documentation provides the standard update procedure through the PolyScope touchscreen interface or via SSH for automated fleet management.
-
Disable the Dashboard Server if not required. In PolyScope 5, the Dashboard Server can be disabled under Settings → System → Network. Cells that do not use the Dashboard Server for integration should turn it off entirely — this removes the attack surface regardless of patch status.
-
Restrict access to TCP 29999. If the Dashboard Server must remain active, enforce network-level access controls so only known and authorised hosts — the specific MES, SCADA, or cell controller — can reach that port. Firewall rules on the OT switch or the controller’s host-based firewall should deny access from all other sources.
-
Audit network paths. Review whether cobot controllers are reachable from IT segments, jump servers, or remote access infrastructure. Controllers should sit behind OT DMZ segmentation and should not be directly addressable from corporate or internet-facing networks.
-
Check for indicators of compromise. Review Dashboard Server logs at
/var/log/ur/for unexpected commands or session activity prior to patching. Any anomalous robot program modifications, speed or force threshold changes, or unexpected network connections from the controller should be treated as a potential compromise.
Broader Risk: Cobots as OT Network Pivot Points
Collaborative robots occupy an awkward position in the OT security model. Unlike traditional PLCs and DCS controllers, cobots are general-purpose Linux systems running a relatively complex software stack with documented network APIs. They are designed to be integrated — vendors encourage connections to MES, ERP, and cloud analytics platforms. That integration story is also a security liability.
Where a traditional Siemens S7 PLC exposes a relatively narrow set of proprietary protocols, a PolyScope 5 controller runs SSH, a Dashboard Server, a web server for the graphical interface, and a REST API. Each of those services is a potential attack surface. When those services are reachable across poorly segmented networks, a cobot fleet becomes an attractive target — not necessarily because the robots themselves are the end goal, but because they provide authenticated, Linux-level access inside the OT network.
The same logic that applies to engineering workstations and HMIs applies to cobot controllers: they are general-purpose computers running industrial software, and they need to be treated accordingly. That means patching on a defined cycle, network segmentation, minimal service exposure, and monitoring for anomalous behaviour — not treated as embedded appliances that are set and forgotten.
CISA Guidance
CISA recommends following ICS defence-in-depth practices: minimise network exposure for all control system devices, place controllers behind firewalls and isolate them from business networks, and use secure remote access methods (VPN with MFA) when remote access is required. The advisory (ICSA-26-134-17) is available on the CISA website.
Universal Robots’ own security advisory and patch notes are published at the Universal Robots cybersecurity portal.