# CVE-2026-105751: Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend

> An attacker can read arbitrary local files by crafting a malicious OpenDocument file, exposing sensitive data to anyone using the Docling library.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA: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:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-4xhp-xg4w-8ppm, PYSEC-2026-4207

## What is CVE-2026-105751?

CVE-2026-105751 is a medium-severity path traversal vulnerability in docling-project docling, published on 5 Oct 2026. 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

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.107.0 until 2.120.3, docling/backend/opendocument_backend.py uses the xlink:href attribute value of a draw:image element as a filesystem path when the referenced part is not found in the document archive. The _image_ref_from_odf_image function reads that attacker-controlled path without a scheme check, extraction-directory confinement, or the enable_local_fetch setting used by other backends. Readable files that Pillow can decode as images are embedded in converted output, and other existing paths can be distinguished through the attempted read. This issue is fixed in 2.120.3.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-105751?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docling` | PyPI | From 2.107.0 | 2.120.3 |
| `docling` | PyPI | From 2.107.0 | 2.120.3 |
| `docling` | PyPI | From 2.107.0 | 2.120.3 |

Products: Docling Docling.

## How do I fix CVE-2026-105751?

Upgrade docling to 2.120.3 or later.

## Is CVE-2026-105751 being exploited?

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

## Other vulnerabilities in docling-project docling

- [CVE-2026-44016](https://insights.sbomify.com/CVE-2026-44016/): Docling: Unsafe Playwright-based HTML Rendering (high 8.2)
- [CVE-2026-105744](https://insights.sbomify.com/CVE-2026-105744/): Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine (high 7.5)
- [CVE-2026-44017](https://insights.sbomify.com/CVE-2026-44017/): Docling: Unsafe Zip Extraction in EasyOCR Model Download (high 7.5)
- [CVE-2026-44020](https://insights.sbomify.com/CVE-2026-44020/): Docling: Unsafe XML Entity Expansion in USPTO Patent Backend (high 7.5)
- [CVE-2026-47214](https://insights.sbomify.com/CVE-2026-47214/): Docling: Unsafe URI and Path Handling in HTML Backend (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105751 and fix it if it is affected.

What it is: CVE-2026-105751 is a medium-severity path traversal vulnerability in docling-project docling, published on 5 Oct 2026. 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-2026-105751 exists.

Affected packages and fixed versions:
- docling (PyPI): affected from 2.107.0; fixed in 2.120.3
- docling (PyPI): affected from 2.107.0; fixed in 2.120.3
- docling (PyPI): affected from 2.107.0; fixed in 2.120.3

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-2026-105751/ (Markdown: https://insights.sbomify.com/CVE-2026-105751/index.md)
```

## Sources

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

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