CVE-2025-9959 Sandbox escape in smolagents Local Python execution environment via dunder attributes
High 7.6
Published
Updated
Check this codebase for CVE-2025-9959 and fix it if it is affected.
What it is: CVE-2025-9959 is a high-severity vulnerability, published on 3 Sep 2025.
Exploitation: There is no known exploitation of CVE-2025-9959 in the wild and no public exploit code.
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-9959/ (Markdown: https://insights.sbomify.com/CVE-2025-9959/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-9959?
CVE-2025-9959 is a high-severity vulnerability, published on 3 Sep 2025.
Official description
Incomplete validation of dunder attributes allows an attacker to escape from the Local Python execution environment sandbox, enforced by smolagents. The attack requires a Prompt Injection in order to trick the agent to create malicious code.
Weakness: CWE-94
Which versions are affected by CVE-2025-9959?
How do I fix CVE-2025-9959?
No fix has been published for CVE-2025-9959 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-9959 being exploited?
There is no known exploitation of CVE-2025-9959 in the wild and no public exploit code.
Sources
Also known as GHSA-p8v6-48p4-f4r4.