CVE-2025-10772
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 · uneditedA vulnerability was identified in huggingface LeRobot up to 0.3.3. Affected by this vulnerability is an unknown functionality of the file lerobot/common/robot_devices/robots/lekiwi_remote.py of the component ZeroMQ Socket Handler. The manipulation leads to missing authentication. The attack can only be initiated within the local network. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceLeRobot up to version 0.3.3 contains a missing authentication vulnerability in the ZeroMQ socket handler within lekiwi_remote.py. An attacker on the local network can connect to the unprotected ZeroMQ socket and interact with robot devices without any authentication credentials.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:L/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.
-
Check LeRobot versionRun 'pip show lerobot' or 'pip list | grep lerobot' to identify the installed version of LeRobotAffected if The installed version is 0.3.3 or earlier (any version up to and including 0.3.3)
-
Locate lekiwi_remote.pySearch for lekiwi_remote.py in the LeRobot installation directory (typically in site-packages/lerobot or the source tree) using 'find /path/to/lerobot -name lekiwi_remote.py'Affected if The file lekiwi_remote.py exists in the installed LeRobot package
-
Verify ZeroMQ is being usedInspect lekiwi_remote.py for ZeroMQ imports (zmq, zmq.auth) and socket creation patterns (zmq.Context, socket.bind)Affected if LeRobot is using ZeroMQ sockets without authentication enabled
-
Check ZeroMQ socket configurationReview the lekiwi_remote.py code around the ZeroMQ bind call to see if ZAP (ZeroMQ Authentication Protocol) or any authentication mechanism is configured. Look for zmq.auth or zmq.AUTH_* settingsAffected if The ZeroMQ socket is bound without any authentication configuration (no ZAP, no certificate, no password)
-
Confirm network exposureCheck if the ZeroMQ socket is bound to a network interface accessible from other hosts (0.0.0.0 or non-loopback IP) rather than localhost onlyAffected if The ZeroMQ socket listens on a network-accessible interface and is reachable from the local network
You are affected if you are running LeRobot version 0.3.3 or earlier and the lekiwi_remote.py component is in use with an unauthenticated ZeroMQ socket exposed to the local network.
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 dataImplement authentication (such as ZAP - ZeroMQ Authentication Protocol) for the ZeroMQ socket, including certificate-based or password-based authentication, and restrict network access to trusted IPs within the local network.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10772 — 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-10772 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