Skip to main content
Cyber News & CTI Reports :: 2026-08-28 | Two Unitree G1 EDU Humanoid Robot Flaws Enable Root RCE, One Starts Over Bluetooth
Contact Page | Privacy Policy

2026-08-28 | Two Unitree G1 EDU Humanoid Robot Flaws Enable Root RCE, One Starts Over Bluetooth

1. AI Summary

Two critical remote code execution vulnerabilities in Unitree G1 EDU robots allow root access via network-adjacent path traversal and BLE proximity. Owners lack verified firmware fixes, leaving devices potentially exposed.

2. IOCs

IOC Type Value Description Relevant MITRE ATT&CK Techniques
Filepath
chat_go
Component in Unitree G1 EDU firmware vulnerable to path traversal T1190
Filepath
bashrunner
Binary used to achieve root execution after path traversal T1203
Vulnerability CVE-2026-76639 Path traversal in chat_go leading to root RCE via bashrunner T1190|T1203|T1068
Vulnerability CVE-2026-76640 BLE proximity chain leading to root RCE via Wi-Fi provisioning buffer overflow T1200|T1203|T1068

3. MITRE ATT&CK

Code Title
T1190 Exploiting network-adjacent path traversal in chat_go to reach bashrunner
T1203 Exploitation for execution leading to remote code execution on the robot
T1068 Exploitation for privilege escalation to obtain root access
T1200 Wireless attack via BLE proximity to initiate the attack chain

4. Targets

Type Value
Region Global
Sector Robotics

5. Article Details

6. Original text

Security researcher Olivier Laflamme has disclosed two independent root remote code execution (RCE) chains affecting the Unitree G1 EDU , including a Bluetooth Low Energy (BLE) path that can reach root on the robot's Locomotion PC. The flaws are tracked as

CVE-2026-76639
and
CVE-2026-76640
, with the first involving a network-adjacent path through
chat_go
and
bashrunner
and the second beginning from BLE proximity. An exact fixed firmware release has not been verified in any accessible Unitree guidance, leaving G1 EDU owners without a confirmed release target for either vulnerability. Laflamme said Unitree patched the cloud account-to-robot ownership check in July 2026. As of the August 27 disclosure, the current cloud-assisted route requires an account bound to the target G1 or the relevant key material already in hand. Laflamme published the research on August 27, 2026, describing the two issues as separate root-RCE paths. The research timeline shows Laflamme upgraded the test robot to V1.5.2, but that sequence does not by itself establish V1.5.1.1 as affected. In his technical disclosure , Laflamme said
CVE-2026-76639
uses a path-traversal condition in
chat_go
to reach
bashrunner
. Execution through
bashrunner
results in root code execution on the Locomotion PC. Laflamme described
CVE-2026-76639
as an independent RCE, although he reused it as one disclosure primitive while demonstrating the separate BLE chain tracked as
CVE-2026-76640
. For
CVE-2026-76640
, the initial BLE write path accepts the bootstrap interaction without Bluetooth pairing. The bootstrap material itself remains protected, and the later Wi-Fi provisioning operations require the application's authenticated BLE state. During Laflamme's research, Unitree's cloud service accepted a valid Unitree account for the key-recovery request but did not verify that the account owned the supplied robot. That authorization gap allowed the account to recover key material associated with another G1 EDU.

The recovered key could then be used to establish the authenticated BLE state required by the Wi-Fi provisioning operations. The chain then reached the Wi-Fi provisioning code. Laflamme documented a buffer overflow there that produced root execution on the Locomotion PC. Laflamme limited his propagation test to two G1 robots in one room. He said in the August 27 disclosure that the cloud authorization fix breaks that exact proof-of-concept flow. Unitree's official product page distinguishes the G1 and G1 EDU as separate models, while broader applicability of the two new vulnerabilities to other Unitree robots remains unconfirmed. The Hacker News has reached out to Unitree to confirm the fixed firmware versions, the affected product scope, and the current remediation status, and will update the story with any response.