# CVE-2025-45466: Hardcoded credentials in n/a

> Attackers can bypass authentication on Unitree Go1 robots using hardcoded plaintext credentials, gaining unauthorized access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2025
- **Updated:** 25 Jul 2025
- **Also known as:** GHSA-87px-4m24-345h

## What is CVE-2025-45466?

CVE-2025-45466 is a high-severity vulnerability in n/a, published on 25 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unitree Go1 <= Go1_2022_05_11 is vulnerale to Incorrect Access Control due to authentication credentials being hardcoded in plaintext.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Unitree Go1 Firmware.

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

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

## Is CVE-2025-45466 being exploited?

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

Public exploit code:

- It is the details of CVE-2025-45466 (github_poc): https://github.com/zgsnj123/CVE-2025-45466

## Other vulnerabilities in n/a

- [CVE-2025-45467](https://insights.sbomify.com/CVE-2025-45467/): Security feature bypass in n/a (high 7.1)
- [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-45466 and fix it if it is affected.

What it is: CVE-2025-45466 is a high-severity vulnerability in n/a, published on 25 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45466 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-45466/ (Markdown: https://insights.sbomify.com/CVE-2025-45466/index.md)
```

## Sources

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

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