# CVE-2025-60017: Command injection in B2

> Attackers can execute arbitrary OS commands with root privileges on Unitree robots via malicious Wi-Fi parameters.

- **Severity:** High 8.2 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-cmhh-362m-7qph

## What is CVE-2025-60017?

CVE-2025-60017 is a high-severity command injection vulnerability in Unitree B2, published on 26 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unitree Go2, G1, H1, and B2 devices through 2025-09-20 allow root OS command injection via the hostapd_restart.sh wifi_ssid or wifi_pass parameter (within restart_wifi_ap and restart_wifi_sta).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-60017?


## How do I fix CVE-2025-60017?

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

## Is CVE-2025-60017 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60017 and fix it if it is affected.

What it is: CVE-2025-60017 is a high-severity command injection vulnerability in Unitree B2, published on 26 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60017 exists.

Affected product: Unitree B2. 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-2025-60017/ (Markdown: https://insights.sbomify.com/CVE-2025-60017/index.md)
```

## Sources

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

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