Skip to main content
CVE-2025-14931VulnerabilityPublished Updated

CVE-2025-14931: Hugging Face smolagents · Deserialization of Untrusted Data

Affects Hugging Face smolagentsSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
PyPIsmolagentspkg:pypi/smolagentsOther threatsAffected
  • =1.22.0
Fixed in–

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

AI-suggested

1. Immediately restrict network access to Hugging Face smolagents instances, limiting exposure to trusted internal networks only. 2. Implement strict input validation and sanitization on all data inputs accepted by smolagents, especially those involving serialized data formats. 3. Monitor network traffic and logs for anomalous or unexpected pickle data payloads indicative of exploitation attempts. 4. Employ application-layer firewalls or intrusion detection/prevention systems configured to detect and block malicious deserialization patterns. 5. Isolate smolagents services in segmented environments with minimal privileges to contain potential compromises. 6. Engage with Hugging Face for official patches or updates and apply them promptly once available. 7. Consider disabling or replacing the vulnerable deserialization functionality if feasible until a patch is released. 8. Conduct security awareness and training for development and operations teams on the risks of unsafe deserialization and secure coding practices. 9. Regularly audit and update dependencies and third-party components to reduce exposure to similar vulnerabilities.

Description

Hugging Face smolagents Remote Python Executor Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Hugging Face smolagents. Authentication is not required to exploit this vulnerability. The specific flaw exists within the parsing of pickle data. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-28312.

References

Community reviews

Loading reviews…