# CVE-2026-105748: Docling: Crafted DoclingDocument JSON embeds local image files into converted output

> Attackers can read local image files by crafting JSON inputs with local paths, exposing sensitive data when embedded image mode is enabled.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/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:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-p944-4xh2-x776, PYSEC-2026-4208, PYSEC-2026-4213

## What is CVE-2026-105748?

CVE-2026-105748 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.16.0 until 2.131.0, the InputFormat.JSON_DOCLING backend in docling/backend/json/docling_json_backend.py validates serialized DoclingDocument input without rejecting picture image references that contain local paths or file URIs. When the document is enriched or exported with ImageRefMode.EMBEDDED, the DoclingDocument._with_embedded_pictures and ImageRef.pil_image methods can open those references and place readable image bytes in Markdown or HTML output. Disclosure is limited to files Pillow can decode as images, while differing decode behavior can also reveal whether a path exists. Direct untrusted loading through docling-core is outside this Docling fix. This issue is fixed in 2.131.0.

Weakness: CWE-73 (External Control of File Name or Path), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

6 open source packages ship an affected version, including docling and docling-slim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docling` | PyPI | From 2.16.0 | 2.131.0 |
| `docling` | PyPI | From 2.16.0 | 2.131.0 |
| `docling` | PyPI | From 2.16.0 | 2.131.0 |
| `docling-slim` | PyPI | From 2.92.0 | 2.131.0 |
| `docling-slim` | PyPI | From 2.92.0 | 2.131.0 |
| `docling-slim` | PyPI | From 2.92.0 | 2.131.0 |

Products: Docling Docling.

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

Upgrade docling to 2.131.0 or later.

## Is CVE-2026-105748 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105748 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-105748 and fix it if it is affected.

What it is: CVE-2026-105748 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-105748 exists.

Affected packages and fixed versions:
- docling (PyPI): affected from 2.16.0; fixed in 2.131.0
- docling (PyPI): affected from 2.16.0; fixed in 2.131.0
- docling (PyPI): affected from 2.16.0; fixed in 2.131.0
- docling-slim (PyPI): affected from 2.92.0; fixed in 2.131.0
- docling-slim (PyPI): affected from 2.92.0; fixed in 2.131.0
- docling-slim (PyPI): affected from 2.92.0; fixed in 2.131.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-2026-105748/ (Markdown: https://insights.sbomify.com/CVE-2026-105748/index.md)
```

## Sources

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

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