CVE-2026-115533 Hugging Face CVE debrief

Who should care

Defenders responsible for deploying and managing LeRobot library instances, especially in environments where dynamic class instantiation is used, should assess exposure and prioritize remediation.

Why it matters

The LeRobot library vulnerability requires verification and remediation in deployments using dynamic class instantiation, especially in environments with policy processor configurations.

• Potential for arbitrary code execution in LeRobot library deployments
• Need for verification and remediation in dynamic class instantiation use cases
• Possible exposure in environments using policy processor configurations

Technical summary

The LeRobot library is vulnerable to arbitrary code execution via unsafe dynamic class instantiation in the from_pretrained() method and related paths. When loading a policy's processor configuration from a repository, the library uses the class field within the JSON configuration to dynamically resolve and instantiate Python classes using importlib.import_module() and getattr(). The vulnerability requires verification and remediation in deployments using dynamic class instantiation, especially in environments with policy processor configurations. Defenders should prioritize verifying and remediating this vulnerability in LeRobot library deployments, especially in environments where dynamic class instantiation

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in LeRobot library deployments, especially in environments where dynamic class instantiation is used.

Recommended defensive actions

• Verify LeRobot library version and configuration
• Assess exposure in dynamic class instantiation use cases
• Implement compensating controls for policy processor configurations
• Review vendor guidance for affected product deployments
• Track exceptions and retest remediated assets
• Check relevant monitoring, detection, and logs for exposed assets
• Confirm whether affected product deployments exist in managed environments

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability, but indicate that it exists in the LeRobot library and involves unsafe dynamic class instantiation. The vulnerability requires verification and remediation in deployments using dynamic class instantiation, especially in environments with policy processor configurations. Defenders should verify the library version and configuration, assess exposure in dynamic class instantiation use cases, and implement compensating controls for policy processor The LeR

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.