# CVE-2025-60250: Weak cryptography in B2

> Attackers can decrypt BLE traffic from Unitree robots using hardcoded keys, exposing sensitive data.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **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-j7cx-968m-v284

## What is CVE-2025-60250?

CVE-2025-60250 is a medium-severity 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 decrypt BLE packet data by using the df98b715d5c6ed2b25817b6f2554124a key and the 2841ae97419c2973296a0d4bdfe19a4f IV.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2025-60250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60250 is a medium-severity 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-60250 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-60250/ (Markdown: https://insights.sbomify.com/CVE-2025-60250/index.md)
```

## Sources

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

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