Description
LeRobot through 0.6.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 products
huggingface: lerobot
References5
- github.com/huggingface/lerobot/pull/3048 Issue TrackingPatch
- chocapikk.com/posts/2026/lerobot-pickle-rce/ ExploitMitigationThird Party Advisory
- github.com/huggingface/lerobot/issues/3047 ExploitIssue TrackingThird Party Advisory
- www.vulncheck.com/advisories/lerobot-unsafe-deserialization-rem… ExploitThird Party Advisory
- github.com/huggingface/lerobot/issues/3134 Issue Tracking
Metrics
- CVSS 3.1
-
9.8
CRITICAL
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 4.0
-
9.3
CRITICAL
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 16% percentile: 97 · as of 13 November 2026
- CWE
- CWE-502
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.