# CVE-2026-27510: Unitree Go2 Mobile Program Tampering Enables Root RCE

> Attackers can inject arbitrary Python code via tampered mobile app programs or shared marketplace items, leading to root remote code execution on the robot.

- **Severity:** Medium 6.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 25 May 2026
- **Also known as:** GHSA-c2p8-28pf-f3mr

## What is CVE-2026-27510?

CVE-2026-27510 is a medium-severity code injection vulnerability in UnitreeRobotics Unitree Go2, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unitree Go2 firmware versions 1.1.7 through 1.1.11, when used with the Unitree Go2 Android application (com.unitree.doggo2), are vulnerable to remote code execution due to missing integrity protection and validation of user-created programmes. The Android application stores programs in a local SQLite database (unitree_go2.db, table dog_programme) and transmits the programme_text content, including the pyCode field, to the robot. The robot's actuator_manager.py executes the supplied Python as root without integrity verification or content validation. An attacker with local access to the Android device can tamper with the stored programme record to inject arbitrary Python that executes when the user triggers the program via a controller keybinding, and the malicious binding persists across reboots. Additionally, a malicious program shared through the application's community marketplace can result in arbitrary code execution on any robot that imports and runs it.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-27510?

It affects 1 product.


Products: Unitree Go2 Firmware.

## How do I fix CVE-2026-27510?

No fix has been published for CVE-2026-27510 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27510 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27510 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27510 and fix it if it is affected.

What it is: CVE-2026-27510 is a medium-severity code injection vulnerability in UnitreeRobotics Unitree Go2, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27510 exists.

Affected product: UnitreeRobotics Unitree Go2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27510/ (Markdown: https://insights.sbomify.com/CVE-2026-27510/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27510
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27510
- OSV: https://osv.dev/vulnerability/CVE-2026-27510

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27510/
Summaries are generated and may contain mistakes; the official description above is the record.