CVE-2026-25874: LeRobot Unsafe Deserialization Remote Code Execution via gRPC

Published Apr 23, 2026
·
Updated

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.

Affected Software

2 affected components
pypi/LeRobot<=0.5.1
huggingface Lerobot Python<=0.5.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Enable TLS for gRPC channels and require authentication (e.g., mTLS or other authentication) so that unauthenticated plaintext gRPC connections are not accepted by the policy server or robot client.

    LeRobot policy server and robot client (gRPC channels) TLS and authentication for gRPC = enabled
  2. Configuration

    Stop using pickle.loads() to deserialize data received over gRPC. Replace unsafe pickle deserialization with a safe deserialization approach and validate inputs before deserializing.

    LeRobot policy server and robot client pickle.loads() deserialization = disabled
  3. Compensating control

    Restrict network reachability of the policy server and robot client gRPC endpoints to trusted hosts/networks (firewall, VPN, network ACLs) to prevent unauthenticated network-accessible attackers from reaching the services.

Event History

Apr 23, 2026
CVE Published
via MITRE·07:45 PM
Data Sourced
via MITRE·07:45 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-25874?

CVE-2026-25874 has a critical severity rating due to its potential for remote code execution.

2

How do I fix CVE-2026-25874?

To fix CVE-2026-25874, ensure the use of authenticated gRPC channels and avoid using pickle.loads() for deserialization.

3

What are the impacts of CVE-2026-25874?

CVE-2026-25874 can allow an attacker to execute arbitrary code on the affected system via unsafe deserialization.

4

Which versions of LeRobot are affected by CVE-2026-25874?

CVE-2026-25874 affects all versions of LeRobot that use unsafe deserialization in the async inference pipeline.

5

Is CVE-2026-25874 exploitable without authentication?

Yes, CVE-2026-25874 is exploitable over unauthenticated gRPC channels, making it particularly dangerous.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203