# CVE-2025-11844: XPath Injection in Hugging Face Smolagents search_item_ctrl_f Function

> Attackers can inject XPath syntax to bypass filters and access unintended DOM elements in Hugging Face Smolagents web automation tasks.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **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:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-8mf9-rmgw-33qc, PYSEC-2026-1930

## What is CVE-2025-11844?

CVE-2025-11844 is a medium-severity vulnerability in huggingface/smolagents, published on 22 Oct 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

Hugging Face Smolagents version 1.20.0 contains an XPath injection vulnerability in the search_item_ctrl_f function located in src/smolagents/vision_web_browser.py. The function constructs an XPath query by directly concatenating user-supplied input into the XPath expression without proper sanitization or escaping. This allows an attacker to inject malicious XPath syntax that can alter the intended query logic. The vulnerability enables attackers to bypass search filters, access unintended DOM elements, and disrupt web automation workflows. This can lead to information disclosure, manipulation of AI agent interactions, and compromise the reliability of automated web tasks. The issue is fixed in version 1.22.0.

Weakness: CWE-643 (Improper Neutralization of Data within XPath Expressions)

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

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


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

Products: Huggingface Smolagents.

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

Upgrade smolagents to 1.22.0 or later.

## Is CVE-2025-11844 being exploited?

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

Public exploit code:

- https://github.com/SparshBiswas-AI/CVE-2025-11844-smolagents (github_poc): https://github.com/SparshBiswas-AI/CVE-2025-11844-smolagents

## Other vulnerabilities in huggingface/smolagents

- [CVE-2025-5120](https://insights.sbomify.com/CVE-2025-5120/): Sandbox Escape Vulnerability in huggingface/smolagents (high 7.6)
- [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-11844 and fix it if it is affected.

What it is: CVE-2025-11844 is a medium-severity vulnerability in huggingface/smolagents, published on 22 Oct 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-11844 exists.

Affected packages and fixed versions:
- smolagents (PyPI): affected all versions; fixed in 1.22.0
- smolagents (PyPI): affected all versions; fixed in 1.22.0
- smolagents (PyPI): affected all versions; fixed in 1.22.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-11844/ (Markdown: https://insights.sbomify.com/CVE-2025-11844/index.md)
```

## Sources

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

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