Two Unitree G1 EDU Humanoid Robot Flaws Enable Root RCE, One Starts Over Bluetooth
Security researcher Olivier Laflamme disclosed two independent root remote code execution (RCE) vulnerabilities (CVE-2026-76639 and CVE-2026-76640) affecting the Unitree G1 EDU humanoid robot CVE-2026-76639 exploits a path-traversal flaw in chat_go to reach bashrunner, achieving root RCE on the robot's Locomotion PC via a network-adjacent attack vector CVE-2026-76640 leverages a BLE proximity-based attack chain: an unauthenticated BLE bootstrap interaction, cloud key-recovery abuse, and a buffer
Analysis
TL;DR
- Security researcher Olivier Laflamme disclosed two independent root remote code execution (RCE) vulnerabilities (CVE-2026-76639 and CVE-2026-76640) affecting the Unitree G1 EDU humanoid robot
- CVE-2026-76639 exploits a path-traversal flaw in chat_go to reach bashrunner, achieving root RCE on the robot's Locomotion PC via a network-adjacent attack vector
- CVE-2026-76640 leverages a BLE proximity-based attack chain: an unauthenticated BLE bootstrap interaction, cloud key-recovery abuse, and a buffer overflow in Wi-Fi provisioning code to achieve root execution
- Unitree patched the cloud account-to-robot ownership verification gap in July 2026, but no confirmed fixed firmware release has been published as of the August 27, 2026 disclosure
- The vulnerabilities are specific to the G1 EDU model; broader applicability to other Unitree robots remains unconfirmed
Why It Matters
This research highlights critical security gaps in humanoid robots that are increasingly deployed in educational, research, and industrial environments, where root-level compromise could lead to physical safety risks, data exfiltration, or device hijacking. The BLE-based attack chain demonstrates how wireless proximity vulnerabilities can bypass traditional network perimeter defenses, a growing concern as IoT and robotics converge. The lack of a verified firmware fix leaves G1 EDU owners in a vulnerable posture, underscoring the importance of responsible disclosure timelines and vendor responsiveness in the robotics sector.
Technical Details
- CVE-2026-76639 (Network-Adjacent RCE): Exploits a path-traversal vulnerability in the
chat_gocomponent, which allows an attacker to reach thebashrunnerservice. Successful exploitation yields root-level code execution on the Locomotion PC without requiring authentication. - CVE-2026-76640 (BLE-Proximity RCE): A multi-stage attack chain beginning with an unauthenticated BLE write path that accepts bootstrap interactions without Bluetooth pairing. The attacker then abuses a cloud service authorization gap (now patched in July 2026) to recover key material for a target robot using any valid Unitree account. The recovered key establishes authenticated BLE state, enabling Wi-Fi provisioning operations where a buffer overflow yields root RCE on the Locomotion PC.
- Cloud Authorization Flaw: During the research period, Unitree's cloud service accepted a valid account for key-recovery requests without verifying that the account actually owned the supplied robot, allowing cross-account key material extraction.
- Affected Firmware: The researcher upgraded the test robot to V1.5.2; however, it was not definitively confirmed whether V1.5.1.1 or other firmware versions are also vulnerable.
- Scope: Vulnerabilities are confirmed on the G1 EDU model. Unitree's official product page distinguishes the G1 and G1 EDU as separate models, and broader applicability remains unconfirmed.
Industry Insight
- Robotics manufacturers must treat wireless interfaces (BLE, Wi-Fi provisioning) as attack surfaces requiring the same security rigor as network-facing services, especially for devices capable of physical interaction with humans.
- Cloud-to-device authentication flows in IoT and robotics ecosystems should enforce strict ownership verification; the patched gap demonstrates how missing authorization checks can enable cross-device key recovery and subsequent local compromise.
- The absence of a verified firmware fix at time of public disclosure poses a significant risk to deployed units—vendors should prioritize rapid patch distribution and clear communication of affected versions to maintain trust in emerging robotic platforms.
Disclaimer: The above content is generated by AI and is for reference only.