Advisories published last week by CISA (Cybersecurity Infrastructure and Security Agency) and Universal Robots, a Danish company specializing in collaborative industrial robots (cobots), reveled a troubling vulnerability impacting UR's robotic control system.
PolyScope 5, an operating system and GUI designed to power and control the company’s cobots, is affected by CVE-2026-8153, an OS command injection vulnerability in the Dashboard Server interface. The flaw, rated critical with a CVSS score of 9.8, has been patched in PolyScope 5.25.1.
The flaw allows the Dashboard Server to accept user-controlled input and pass it to the underlying operating system without proper neutralization of special elements. An unauthenticated attacker with network access to the Dashboard Server port can craft commands that are executed on the robot’s operating system, leading to remote code execution and compromise of the controller.
Basically, hackers could take control of the robot remotely.
Universal Robots noted in its advisory that remote exploitation of CVE-2026-8153 requires the robot’s Dashboard Server to be enabled in the UI, and its port to be reachable by the attacker. UR robots are not designed to be accessible directly from the Internet, and direct inbound Internet access is typically prevented by the company firewall.
So while the likelihood of a DDoS or remote access hack is low, the possibility of such an exploit led many in the cybersecurity community of voice concerns over where bad actors could go with such an opening.
Morey Haber, Chief Security Advisor at BeyondTrust
"The danger behind CVE-2026-8153 is not simply another vulnerability flaw in an Operation Technology environment. It is the reality that an industrial robot controller designed to automate physical processes can potentially be manipulated like a compromised server in a traditional IT environment.
"In the case of the PolyScope 5 Dashboard Server from Universal Robots, the risk extends beyond data theft and directly into manufacturing safety, production integrity, and the bottom line, financially, for any organizations operating the device.
"The exploit is based on command injection and especially dangerous because the exploit often provides threat actors with the ability to execute arbitrary operating system commands. In a robotic environment, that can translate into unauthorized modification of workflows, shutdown of robotic processes, manipulation of configurations, or even disruption of safety controls.
"If exploitation is successful, the robot no longer behaves as a deterministic industrial asset and becomes an adversary controlled endpoint inside the operational network. The downside becomes exponentially worse in environments where robots are interconnected with MES platforms, ERP systems, remote maintenance solutions, or flat networks that do not adhere to the Perdue Model for OT architecture and security.
"A single exploited robot controller could become the pivot point for lateral movement across an entire production environment. Threat actors could deploy ransomware, manipulate production output, exfiltrate intellectual property, or intentionally create downtime that impacts supply chains, revenue generation, and depending on the product produced, intrusive regulatory scrutiny.
"The impact of information security teams and OT engineers’ impact is equally severe. Industrial automation is built on trust, repeatability, high availability, and safety. Vulnerabilities like this challenge all four assumptions simultaneously and organizations often assume robots are appliances rather than fully networked assets with operating systems and applications.
"That misconception creates blind spots in vulnerability and patch management, network segmentation, identity security, and privileged access management. In modern manufacturing, a compromised robot is no longer just an IT problem. It is a business continuity problem, a safety problem, a financial risk, and potentially a geopolitical concern for an advanced attack."
Shane Barney, CISO, Keeper Security
"A critical OS command injection vulnerability in an industrial robot controller is a serious reminder that Operational Technology security cannot be treated as a secondary concern and must be sufficiently segmented from IT environments. CVE-2026-8153 requires no authentication to exploit, meaning an attacker with network access to the affected port can execute commands directly on the robot's operating system.
"That's not a theoretical risk. That's a foothold into a production environment.
"The question of how much organizations should prioritize this comes down to one thing: network exposure. If your UR cobots sit behind properly segmented OT networks with no lateral access from IT systems or third-party connections, your immediate risk is lower.
"But in my experience, that level of segmentation is the exception, not the rule. Many industrial environments have evolved organically, with IT and OT systems sharing infrastructure in ways that weren't fully mapped or hardened. Those are the environments where a vulnerability like this turns into a serious incident.
"The business impact of a compromised robot controller extends well beyond data. Attackers can disrupt production lines, alter operational parameters or use the controller as a pivot point to reach other systems on the network. In manufacturing, downtime has a direct cost, and depending on the application, safety implications as well.
"Affected organizations must update to PolyScope 5.25.1. For those who can't patch immediately, they should disable the Dashboard Server interface if it isn't actively needed and restrict network access at the firewall. More broadly, enforcing least-privilege access controls and maintaining real-time visibility into privileged sessions across converged IT and OT environments are the kind of controls that contain the blast radius when a vulnerability like this is exploited – and that catch the lateral movement that follows.
"Use this moment to audit what else on your OT network is reachable that shouldn't be. Incidents like this have a way of revealing gaps that existed long before the CVE was published. Use this moment to audit your broader OT network exposure. Flat network segments, dormant credentials and unmonitored devices rarely appear on a patch list, but they're exactly what attackers exploit once they're inside."
