Unauthenticated code execution via gRPC pickle deserialization
Published Apr 23, 2026 · Updated Apr 23, 2026
Unsafe deserialization in Hugging Face LeRobot through 0.5.1 allows remote attackers to execute arbitrary code through gRPC. Policy server and robot client handlers pass unauthenticated gRPC byte fields to pickle.loads() before type validation. Any network host that can reach SendPolicyInstructions or SendObservations can compromise the server, while a malicious server can compromise a connecting client.
Summary
What happened
Unsafe deserialization in Hugging Face LeRobot through 0.5.1 allows remote attackers to execute arbitrary code through gRPC. Policy server and robot client handlers pass unauthenticated gRPC byte fields to pickle.loads() before type validation. Any network host that can reach SendPolicyInstructions or SendObservations can compromise the server, while a malicious server can compromise a connecting client.
The record
- CVE
- CVE-2026-25874
- Published
- Apr 23, 2026
- Updated
- Apr 23, 2026
- Vendor
- Hugging Face
- Product
- LeRobot
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2026CVE publishedPublication date reported by the CVE source.
- Apr 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.5.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- LeRobot gRPC pickle RCE proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo