# CVE-2025-45467: Security feature bypass in n/a

> Attackers can bypass firmware integrity checks using MD5 collisions to install malicious firmware on Unitree Go1 robots via network interfaces.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/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:** 25 Jul 2025
- **Updated:** 25 Jul 2025
- **Also known as:** GHSA-56gq-m2m7-qc85

## What is CVE-2025-45467?

CVE-2025-45467 is a high-severity vulnerability in n/a, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unitree Go1 <= Go1_2022_05_11 is vulnerable to Insecure Permissions as the firmware update functionality (via Wi-Fi/Ethernet) implements an insecure verification mechanism that solely relies on MD5 checksums for firmware integrity validation.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Unitree Go1 Firmware.

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

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

## Is CVE-2025-45467 being exploited?

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

Public exploit code:

- https://github.com/zgsnj123/CVE-2025-45467 (github_poc): https://github.com/zgsnj123/CVE-2025-45467

## Other vulnerabilities in n/a

- [CVE-2025-45466](https://insights.sbomify.com/CVE-2025-45466/): Hardcoded credentials in n/a (high 8.8)
- [CVE-2025-2894](https://insights.sbomify.com/CVE-2025-2894/): Unitree Go1 Robot Dog Backdoor Control Channel (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45467 is a high-severity vulnerability in n/a, published on 25 Jul 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-45467 exists.

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

## Sources

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

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