Unitree G1 CVE-2026-76639, alongside CVE-2026-76640, is one of two independent root remote code execution chains disclosed in the Unitree G1 EDU humanoid robot, including a Bluetooth Low Energy path that can reach root on the robot's Locomotion PC. Security researcher Olivier Laflamme disclosed the pair on August 27, 2026, and no confirmed fixed firmware release has been identified in accessible Unitree guidance, leaving owners without a clear patch target. As robots move from labs into workplaces, a root-level compromise of one is a serious physical and data security concern, not a novelty.

The two chains reach root by different routes. CVE-2026-76639 (CVSS 8.7, CWE-22) uses a path-traversal condition in a component called chat_go to reach bashrunner, and execution through bashrunner yields root code execution on the Locomotion PC over a network-adjacent path. CVE-2026-76640 (CVSS 7.7, CWE-306) begins from Bluetooth proximity: the initial BLE write path accepts the bootstrap interaction without Bluetooth pairing, though the bootstrap material itself remains protected and later Wi-Fi provisioning still requires the application's authenticated BLE state. Laflamme noted Unitree patched a separate cloud account-to-robot ownership check in July 2026.

How serious are these robot vulnerabilities?

Serious, because root on the Locomotion PC means control of the machine that moves the robot, plus access to whatever data and networks it touches. The BLE path is the more striking of the two: accepting a bootstrap write without pairing means an attacker within Bluetooth range has a starting foothold, which is a very different threat model from a purely network-based bug. The saving grace is that the current cloud-assisted route requires an account already bound to the target robot or the relevant key material in hand, so the easiest remote path was tightened, but the local chains remain.

What should owners of these robots do?

Reduce proximity and network exposure while a firmware fix is unclear. Keep the robot off untrusted networks and segment it from sensitive systems, treat Bluetooth range as an attack surface by operating it away from untrusted parties, and watch Unitree channels for a firmware release that names these CVEs. Because there is no confirmed patch, the practical posture is containment: limit who and what can reach the robot over the network and over Bluetooth.

Our read

A humanoid robot is a computer with actuators and sensors, and CVE-2026-76639 is a reminder that it inherits every category of software flaw plus a physical one. The lesson generalizes to the whole class of capable connected devices entering workplaces: they need the same threat modeling, segmentation, and patch expectations as any other endpoint, not a pass because they are new. Understanding that risk before deployment, rather than after a root compromise, is the difference between an experiment and an exposure.

Reporting by The Hacker News; vulnerability detail per Olivier Laflamme's disclosure; CVSS and CWE per NVD. Sources linked above.

Related: AI agent security in 2026 and What is a zero-day?.