Security readout for executives and security teams
Plain-English summary
CVE-2026-27510 affects Unitree Go2 robot firmware 1.1.7 through 1.1.11 used with the Unitree Go2 Android app. A tampered or shared user program can run Python code on the robot as root when a user runs it. For organizations using Go2 robots, this is a high-impact control and safety concern.
Executive priority
Treat as urgent for any organization operating affected Go2 robots. The issue can give root-level control of the robot after user interaction, creating business, operational, and potential physical-risk exposure. Prioritize inventory, access control, and vendor update tracking.
Technical view
The issue is missing integrity protection and validation for user-created programs. The Android app stores program content in a local SQLite database and sends programme_text, including pyCode, to the robot. The robot component actuator_manager.py executes supplied Python as root. The CVSS score is 9.6, with user interaction required.
Likely exposure
Exposure is limited to Unitree Go2 deployments running firmware 1.1.7 through 1.1.11 with the Unitree Go2 Android application. Risk is higher where Android devices are shared, weakly controlled, or where users import community marketplace programs.
Exploitation context
The sources describe two paths: local tampering on the Android device before a user triggers the program, and malicious programs shared through the app marketplace. The provided bundle does not report CISA KEV listing or confirmed active exploitation in the wild.
Researcher notes
Evidence comes from the CVE record, VulnCheck advisory, and a technical write-up. The public description names the storage path, trust failure, affected firmware range, and root execution context. Do not assume a vendor patch is available unless Unitree publishes one.
Mitigation direction
- Check Unitree guidance and firmware/app updates for CVE-2026-27510.
- Restrict physical and local access to Android devices controlling Go2 robots.
- Avoid importing or running community-shared programs until vendor guidance is available.
- Inventory Go2 firmware versions and prioritize 1.1.7 through 1.1.11.
- Use only trusted, reviewed programs on affected robots.
Validation and detection
- Identify Unitree Go2 robots and record firmware versions.
- Confirm whether the Unitree Go2 Android app is used.
- Review whether community marketplace programs have been imported.
- Inspect operational procedures for shared or unmanaged controller Android devices.
- Monitor vendor and advisory pages for updated remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-27510 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://boschko.ca/unitree-go2-rce/CVE reference · technical-description, exploit
- https://shop.unitree.com/products/unitree-go2CVE reference · product
- https://www.vulncheck.com/advisories/unitree-go2-mobile-program-tampering-enables-root-rceCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.