# CVE-2025-5120: Sandbox Escape Vulnerability in huggingface/smolagents

> Attackers can bypass sandbox restrictions in huggingface/smolagents to execute arbitrary code on the host system, leading to remote code execution and data leakage.

- **Severity:** High 7.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-6v92-r5mx-h5fx, PYSEC-2026-542

## What is CVE-2025-5120?

CVE-2025-5120 is a high-severity code injection vulnerability in huggingface/smolagents, published on 27 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A sandbox escape vulnerability was identified in huggingface/smolagents version 1.14.0, allowing attackers to bypass the restricted execution environment and achieve remote code execution (RCE). The vulnerability stems from the local_python_executor.py module, which inadequately restricts Python code execution despite employing static and dynamic checks. Attackers can exploit whitelisted modules and functions to execute arbitrary code, compromising the host system. This flaw undermines the core security boundary intended to isolate untrusted code, posing risks such as unauthorized code execution, data leakage, and potential integration-level compromise. The issue is resolved in version 1.17.0.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-5120?

3 open source packages ship an affected version, including smolagents. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `smolagents` | PyPI | All versions | 1.17.0 |
| `smolagents` | PyPI | All versions | 1.17.0 |
| `smolagents` | PyPI | All versions | 1.17.0 |

Products: Huggingface Smolagents.

## How do I fix CVE-2025-5120?

Upgrade smolagents to 1.17.0 or later.

## Is CVE-2025-5120 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5120 exists.

## Other vulnerabilities in huggingface/smolagents

- [CVE-2025-11844](https://insights.sbomify.com/CVE-2025-11844/): XPath Injection in Hugging Face Smolagents search_item_ctrl_f Function (medium 5.4)
- [CVE-2026-4963](https://insights.sbomify.com/CVE-2026-4963/): huggingface smolagents Incomplete Fix CVE-2025-9959 local_python_executor.py evaluate_with code injection (medium 5.3)
- [CVE-2026-2654](https://insights.sbomify.com/CVE-2026-2654/): huggingface smolagents LocalPythonExecutor requests.post server-side request forgery (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5120 and fix it if it is affected.

What it is: CVE-2025-5120 is a high-severity code injection vulnerability in huggingface/smolagents, published on 27 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5120 exists.

Affected packages and fixed versions:
- smolagents (PyPI): affected all versions; fixed in 1.17.0
- smolagents (PyPI): affected all versions; fixed in 1.17.0
- smolagents (PyPI): affected all versions; fixed in 1.17.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5120/ (Markdown: https://insights.sbomify.com/CVE-2025-5120/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5120
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5120
- OSV: https://osv.dev/vulnerability/CVE-2025-5120

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5120/
Summaries are generated and may contain mistakes; the official description above is the record.