Two Unitree G1 EDU Humanoid Robot Flaws Enable Root RCE, One Starts Over Bluetooth
- ID
- 19045
- Status
- summarized
- Published
- 28 Aug 2026, 8:07 PM
- Fetched
- 28 Aug 2026, 9:37 PM
- Provider
- The Hacker News
- Category
- security
- Original URL
- https://thehackernews.com/2026/08/two-unitree-g1-edu-humanoid-robot-flaws.html
- Source URL
- https://feeds.feedburner.com/TheHackersNews
Summary
- Score
- 4.0
- Created
- 28 Aug 2026, 9:39 PM
- Tags
- Audience
- developersai_agent_users
What happened
Security researcher Olivier Laflamme disclosed two independent root RCE chains (CVE-2026-76639, CVE-2026-76640) in the Unitree G1 EDU humanoid robot. One chain exploits a path-traversal in chat_go reaching bashrunner for root execution on the Locomotion PC; the other starts over Bluetooth Low Energy without pairing, abuses a cloud authorization gap to recover another robot's key material, then exploits a buffer overflow in Wi-Fi provisioning code. Unitree patched the cloud ownership check in July 2026, but no confirmed fixed firmware version exists for either vulnerability as of August 27, 2026.
Why it matters
If you operate or are evaluating a Unitree G1 EDU, there is no verified patched firmware to upgrade to — the only mitigation is restricting physical/Bluetooth proximity and network access to the robot. For builders working on BLE provisioning or cloud-to-device authorization flows, this is a concrete lesson: a missing ownership check on a key-recovery endpoint can turn a proximity-only attack into full root RCE.
Discussion angle
The design pattern that failed here — cloud service accepting any valid account for key recovery without verifying robot ownership — is a class of authorization bug worth checking in your own IoT or agent-orchestration systems where a cloud service hands out device credentials.