dbcve.org
LerobotApplication · Huggingface

CVE-2026-25874

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to after 0.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
LeRobot through 0.5.1 contains an unsafe deserialization vulnerability in the async inference pipeline where pickle.loads() is used to deserialize data received over unauthenticated gRPC channels without TLS in the policy server and robot client components. An unauthenticated network-reachable attacker can achieve arbitrary code execution on the server or client by sending a crafted pickle payload through the SendPolicyInstructions, SendObservations, or GetActions gRPC calls.

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 · high confidence

LeRobot through 0.5.1 uses pickle.loads() to deserialize data from unauthenticated gRPC connections without TLS encryption. An attacker can send malicious pickle payloads via SendPolicyInstructions, SendObservations, or GetActions gRPC calls to achieve arbitrary code execution on affected policy servers or robot clients.

MitigationReplace pickle deserialization with safe formats (e.g., JSON, MessagePack) and implement TLS with mutual authentication on all gRPC channels to prevent unauthenticated deserialization attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LerobotApplication
Affected:<= 0.5.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check LeRobot version
    Run 'pip show lerobot' or 'pip list | grep lerobot' to identify the installed version. Compare it to the affected range: versions 0.5.1 and below.
    Affected if The installed version is 0.5.1 or lower.
  2. Identify gRPC usage in deployment
    Search codebase or running services for imports of 'grpc' or usage of SendPolicyInstructions, SendObservations, or GetActions gRPC methods.
    Affected if The application uses these specific gRPC methods for inter-process or inter-system communication.
  3. Verify TLS encryption on gRPC channels
    Inspect gRPC server and client configuration for 'ssl' or 'tls' settings, or inspect the connection setup code for credentials configuration.
    Affected if TLS encryption is NOT enabled on the gRPC channels used for LeRobot communication.
  4. Confirm authentication is enforced on gRPC service
    Review gRPC service configuration or code to determine if authentication tokens, credentials, or mTLS are required for client connections.
    Affected if Authentication is NOT required or enforced on the gRPC service endpoints.

You are affected if LeRobot version 0.5.1 or lower is installed AND gRPC communication channels lack both TLS encryption and authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.5.1
Vendor patch github.com →
Interim mitigation

Replace pickle deserialization with safe formats (e.g., JSON, MessagePack) and implement TLS with mutual authentication on all gRPC channels to prevent unauthenticated deserialization attacks.

Recommended fix Moderate confidence

Latest stable release after version 0.5.1 that incorporates the PR #3048 fix

  1. 1. Review the patch details at the vendor PR: https://github.com/huggingface/lerobot/pull/3048 to understand the code changes made
  2. 2. Ensure all policy server and robot client deployments are identified in your environment
  3. 3. If a patched release is available (version > 0.5.1), upgrade all LeRobot instances to the latest stable release
  4. 4. If no patched release is available yet, apply the code changes from PR #3048 which removes unsafe pickle.loads() usage
  5. 5. After patching, verify the gRPC channels now use proper serialization (such as JSON, protobuf, or safe object serialization)
  6. 6. Enable TLS on all gRPC communications between policy server and robot clients
  7. 7. Implement authentication on gRPC endpoints if not already present
  8. 8. Test the inference pipeline to confirm normal operation after changes
Caveat If the fix changes the serialization format, robot clients and policy servers must be updated simultaneously to maintain compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lerobot Scoped from the published advisory
  • Consultation6.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
48.0 hours of engineering $8,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25874 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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