CVE-2025-60251
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnitree Go2, G1, H1, and B2 devices through 2025-09-20 accept any handshake secret with the unitree substring.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnitree robot devices (Go2, G1, H1, B2) have a weak authentication mechanism during handshake where they accept any secret containing the substring 'unitree' rather than requiring the exact correct secret. This allows an attacker who knows this substring to potentially bypass authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Unitree robot devices on your networkInventory all networked devices and identify Unitree models Go2, G1, H1, or B2 by checking device hostnames, MAC OUI (Unitree manufacturer), or by accessing device management interfaces to confirm the modelAffected if Your environment contains any Unitree Go2, G1, H1, or B2 robot devices
-
Verify management interface network exposureScan your network for accessible management interfaces on the Unitree devices (typically ports 80, 443, or vendor-specific ports). Check firewall rules and network segmentation to determine if these interfaces are reachable from untrusted networksAffected if The device management interface is accessible from networks beyond the trusted local segment
-
Confirm authentication is in useAccess the device handshake or authentication mechanism and observe whether a shared secret is required. This may be configurable in device settings or documented in the robot's API/SDKAffected if The device uses a shared secret for authentication during handshake and that secret can be set or discovered
-
Check if secret contains the substringIf you have access to configure or view the authentication secret, verify whether the current secret contains 'unitree' as a substring. The vulnerability allows any secret with 'unitree' to be acceptedAffected if The configured authentication secret contains the substring 'unitree' (case-insensitive)
You are affected if you have any Unitree Go2, G1, H1, or B2 devices with their management interface network-accessible and using authentication where a secret containing 'unitree' is accepted as valid.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to vendor-supplied firmware/patches when available and ensure network access to device management interfaces is restricted. Review and rotate any exposed credentials.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60251 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data