CVE-2025-14931

10.0

Hugging Face · smolagents

Hugging Face smolagents suffers from a critical deserialization vulnerability in its Remote Python Executor, allowing unauthenticated attackers to achieve remote code execution.

Executive summary

A critical deserialization vulnerability in Hugging Face smolagents allows unauthenticated remote attackers to execute arbitrary code with the privileges of the service account.

Vulnerability

The vulnerability exists due to improper validation of user-supplied pickle data within the Remote Python Executor. This flaw allows an unauthenticated remote attacker to trigger the deserialization of untrusted data, resulting in arbitrary code execution.

Business impact

The ability for an unauthenticated attacker to execute arbitrary code constitutes a total compromise of the affected system, warranting the maximum CVSS score of 10.0. This risk encompasses complete loss of data confidentiality, integrity, and availability, potentially leading to unauthorized system control and lateral movement within the network.

Remediation

Immediate Action: Review the official Hugging Face security advisories for the release of a patched version of smolagents and apply the update immediately upon availability.

Proactive Monitoring: Monitor network traffic and application logs for unusual serialized data patterns or unexpected process execution spawned by the smolagents service.

Compensating Controls: Implement strict network segmentation to isolate the Remote Python Executor from untrusted network segments and apply egress filtering to prevent the service from initiating unauthorized outbound connections.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the critical nature of this vulnerability and the potential for full system compromise, organizations should prioritize isolating affected instances of smolagents. Users must remain vigilant for patch notifications from the vendor and apply updates as soon as they are released to neutralize this high-risk vector.

More Hugging Face CVEs

History

  1. Disclosed CVE record published
  2. Published in the daily brief critical section
  3. Analyst report written

Sources