CVE-2026-25874
CVE-2026-25874 — LeRobot Unsafe Deserialization Remote Code Execution via gRPC
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.
Published Updated Sources: cvelistV5, VulnCheck
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
16%
chance of exploitation in 30 days
CVSS base
9.3
CRITICAL
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
PoC
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 9.3 | CVSS 4.0 | CRITICAL | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-502
References
5 on the record
- chocapikk.com/posts/2026/lerobot-pickle-rce/
exploit
- github.com/huggingface/lerobot/issues/3047
issue-tracking
- github.com/huggingface/lerobot/pull/3048
issue-tracking
- github.com/huggingface/lerobot/issues/3134
issue-tracking
- www.vulncheck.com/advisories/lerobot-unsafe-deserialization-remote-code-execution-via-grpc
third-party-advisory
Elsewhere on this site
- hugging faceevery CVE for this vendor
- CWE-502other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.