External risk intelligence

Universal Robots PolyScope could allow internal attacker to take control of the robot

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-8153

The vulnerable component is an industrial robot controller designed for use in closed manufacturing or operational technology environments. These systems are typically deployed behind firewalls and are not intended for direct connectivity to the public internet. Consequently, the interface is expected to be isolated from public exposure in standard, well-configured deployments.

OS Command Injection

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

An unauthenticated attacker can execute arbitrary code on a robot's operating system through the Dashboard Server interface in Universal Robots PolyScope. This allows an attacker to potentially take full control of the robot.

Control industrial robots remotely.
Affects systems in manufacturing.
Code execution on critical infrastructure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can abuse the Dashboard Server interface to inject operating system commands. This allows them to execute arbitrary code on the robot's operating system, potentially taking full control of the industrial robot.

Network access is sufficient.
Target: Dashboard Server interface.
No user interaction needed.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability allows unauthenticated command execution on industrial robot controllers, a serious concern given the critical nature of automated manufacturing. While the Dashboard Server interface is the entry point, its typical deployment within isolated operational technology (OT) networks may limit direct external attack vectors. However, successful exploitation could lead to significant disruption or manipulation of industrial processes.

Exploitation requires internal network access.
No public exploit code is available.
The vulnerability is not actively exploited.

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize containment of Universal Robots PolyScope systems running versions prior to 5.25.1, as unauthenticated command injection could lead to code execution on the robot's operating system. Given the critical severity and potential for widespread impact in industrial environments, isolate affected services if they are exposed externally or if immediate patching is not feasible.

Block network access to vulnerable interfaces.
Monitor network traffic for suspicious commands.
Upgrade to PolyScope version 5.25.1 or later.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the nature of the vulnerability in Universal Robots PolyScope?

The vulnerability in Universal Robots PolyScope is an OS command injection flaw within the Dashboard Server interface. This allows an unauthenticated attacker to craft commands that result in code execution on the robot's operating system, potentially leading to full control of the robot.

How can an attacker exploit the Universal Robots PolyScope vulnerability?

An attacker can exploit this vulnerability by crafting specific commands to inject into the Dashboard Server interface. This injection allows for the execution of arbitrary code on the robot's operating system. Network access is sufficient for exploitation, and no user interaction is required.

What is the weakness class associated with CVE-2026-8153?

The weakness class associated with CVE-2026-8153 is CWE-78, which corresponds to "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')".

What is the relevance of the Halo Surface Signal for this vulnerability?

The Halo Surface Signal indicates this vulnerability is 'Very unlikely' to be exposed externally. This is because the vulnerable component, an industrial robot controller, is typically deployed in isolated operational technology environments behind firewalls, limiting direct public internet connectivity.

What actions should be taken to address the Universal Robots PolyScope vulnerability?

To address this vulnerability, organizations should prioritize containing Universal Robots PolyScope systems running versions prior to 5.25.1. Isolate affected services if exposed externally or if immediate patching is not feasible. Blocking network access to vulnerable interfaces, monitoring network traffic for suspicious commands, and upgrading to PolyScope version 5.25.1 or later are recommended.

References

www.universal-robots.com/developer/communication-protocol/dashboard-server/

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.