Two unauthenticated remote code execution vulnerabilities (CVE-2026-27509 & CVE-2026-27510) in Unitree robots allow root-level command execution; the first exploits the DDS DataWriter in the actuator manager to run arbitrary Python code, while the second involves tampering with preprogrammed action blocks in the Android app's local database, with both exploits triggered via the physical controller. The vulnerabilities were found in firmware versions V1.1.7 and V1.1.11, respectively. The disclosure timeline indicates Unitree responded and began remediation, but the article does not specify a fixed version, CVSS score, or a formal workaround.
This is a lengthy technical write-up of CVE-2026-27509 and CVE-2026-27510, found alongside @Ruikai, founder of Pwn0 . We both threw in cash for the robot, and I invaded his living space for seven days of chipotle-fueled hacking. Regardless of who found what, weโll be reporting everything together. Keep an eye on his blog for deep technical write-ups on the other vulnerabilities we found. The blog is split into two parts that build on each other. Part one covers CVE-2026-27509, the unauthenticated RCE as root on V1.1.7, achieved by abusing the rt/api/programming_actuator/* DDS DataWriter to execute arbitrary Python. Part two, CVE-2026-27510, takes what we learned and introduces a new exploit primitive targeting the same actuator_manager in V1.1.11, this time by tampering with the Blockly preprogrammed action blocks stored in the Android app's local database. Both PoCs are triggered by pressing a keybinding on the physical controller. That was a big goal of ours and made buying the $400 controller feel worth it ๐ญ. More importantly, the controller trigger makes the RCE persistent. Unitree ( Hangzhou Yushu Technology Co., Ltd . ๆญๅทๅฎๆ ็งๆๆ้ๅ ฌๅธ) is a Chinese developer of advanced consumer and commercial robots, founded in 2016 and based in Hangzhou, China. The company is known for its highโperformance quadrupedal robots (robot dogs) and, more recently, for affordable humanoids such as the R1 and the Rizz Robot (G1) . Unitree was recently in the spotlight for their humanoid robots performing an advanced martial arts routine at China's 2026 Lunar New Year Gala. Image source: https://www.techeblog.com/unitree-robot-2026-chinese-new-year-spring-festival-gala/ Unitree has been publicly advancing plans toward an IPO on Shanghai's STAR Market, targeting a valuation of around ยฅ50 billion (~$7 billion). As of a few weeks ago, Unitree humanoid robots were made available for direct purchase through Amazon. Disclosure Timeline Unitree is clearly working to rebuild trust with the security community after the Unipwn incident. Despite being stretched extremely thin (they need more security headcount IMHO), the team always responded promptly and respected our work as security researchers. "Ixonz" from their security team deserves a special shoutout for being responsive, and professional throughout disclosure. October 24, 2025 โ Received the Unitree G02 robot. October 26, 2025 โ Discovered the DDS vulnerability on firmware V1.1.7 ๐ October 27, 2025 โ Drafted the initial technical blog detailing the PoC and findings. October 29, 2025 โ Contacted Unitree at security@unitree.com to ask for the proper channels for responsible disclosure. October 30, 2025 โ Unitree security responded, we shared technical details and a demo video, and they asked us to validate the PoC on V1.1.11. October 30, 2025 โ The original V1.1.7 PoC no longer worked on V1.1.11 due to suppressed DDS topics. October 30, 2025 โ Discovered the local database modification RCE leveraging the same underlying vulnerable code that achieved RCE on V1.1.11 ๐ November 03, 2025 โ Submitted evidence for the V1.1.11 RCE to Unitree, including a demo video and POC code to assist with validating V1.1.7. November 07, 2025 โ Unitree replied, validating the DDS exposure & accessibility of DDS topics on v1.1.7 and v1.1.11 ( EDU version ). November 06, 2025 โ The technical report was shared outside of Unitree, without our consent, and was unknowingly shared on X by a researcher at a Chinese security lab โน๏ธ. November 07, 2025 โ We informed Unitree that the unindexable, unsitemapped, tagged, tracked, custom URL provided exclusively to them had somehow been redistributed without our knowledge. It was taken down, and communication moved from Email to Telegram. November 07, 2025 โ The researcher on X was contacted & the tweet removed. (We believe this was an honest mistake. Regardless, they should not have had access to the link.) November 10, 2025 โ The Unitree security team validated & reproduced the DDS exploit on versions V1.1.7-V1.1.11 EDU. November 18, 2025 โ The Unitree security team validated & reproduced the mobile DB modification that led to RCE, affecting at minimum version V1.1.7-V1.1.11. November 19, 2025 โ Unitree launched their official responsible disclosure program https://security.unitree.com . December 30, 2025 โ Follow-up and 60-day disclosure notice. Unitree's security team mentioned they had pushed a fix for CVE-2026-27510. We did not retest. A Fix for CVE-2026-27510 was mentioned to be in progress. January 5, 2026 โ Attempted to reserve CVE through a CNA. February 20, 2026 โ Reached out to VulnCheck to obtain CVEs & two were reserved within hours. Unitree was notified the same day, along with the date of intended publication. February 24, 2026 โ Unitree confirmed patches exist and R&D is working on remediation, though internal delays have repeatedly pushed back deployment. February 27, 2026 โ Publishing blog ๐ Affected Versions The following firmware versions of the Unitr...