# CVE-2026-47214: Docling: Unsafe URI and Path Handling in HTML Backend

> Attackers can exploit unsafe URI and path handling in the HTML backend to read arbitrary files or cause denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-q29v-xc37-wh5m, PYSEC-2026-2146

## What is CVE-2026-47214?

CVE-2026-47214 is a high-severity path traversal vulnerability in docling-project docling, published on 26 Jun 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. Prior to 2.94.0, the HTML backend has unsafe URI and path handling. This vulnerability is fixed in 2.94.0.

Weakness: CWE-73 (External Control of File Name or Path), CWE-400 (Uncontrolled Resource Consumption)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docling` | PyPI | All versions | 2.94.0 |
| `docling` | PyPI | All versions | 2.94.0 |
| `docling` | PyPI | All versions | 2.94.0 |

Products: Docling Docling.

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

Upgrade docling to 2.94.0 or later.

## Is CVE-2026-47214 being exploited?

There is no known exploitation of CVE-2026-47214 in the wild and no public exploit code.

## 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-105751](https://insights.sbomify.com/CVE-2026-105751/): Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47214 is a high-severity path traversal vulnerability in docling-project docling, published on 26 Jun 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: There is no known exploitation of CVE-2026-47214 in the wild and no public exploit code.

Affected packages and fixed versions:
- docling (PyPI): affected all versions; fixed in 2.94.0
- docling (PyPI): affected all versions; fixed in 2.94.0
- docling (PyPI): affected all versions; fixed in 2.94.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-47214/ (Markdown: https://insights.sbomify.com/CVE-2026-47214/index.md)
```

## Sources

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

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