Skip to main content
VulnerabilityPublished Updated

CVE-2026-25874: Hugging Face LeRobot · Deserialization of Untrusted Data

Affects Hugging Face LeRobotSource CVE Database V5

0
Compare

Not known to be exploited · 15% EPSS · CVSS 9.3 Critical.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
15.5% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Hugging FaceLeRobotAffected
  • <=0.5.1
Fixed in–
GitHubhuggingface/lerobotpkg:github/huggingface/lerobotOther threatsAffected
  • =0
  • <=0.5.1
Fixed in–
GitHubLeRobotpkg:github/LeRobotOther threatsAffected
  • <=0.5.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, it is recommended to restrict network access to the affected gRPC services, implement TLS to secure communication channels, and avoid sending untrusted data to the vulnerable deserialization endpoints. Monitor vendor channels for updates and apply patches promptly once released.

Description

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.

References

Community reviews

Loading reviews…