# CVE-2026-105746: Docling: KServe v2 OCR engine does not enforce enable_remote_services

> Attackers can bypass remote service restrictions in Docling's KServe v2 OCR engine, forcing unintended network requests despite disabled remote service settings.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-h42j-9hcc-3cwc, PYSEC-2026-4193

## What is CVE-2026-105746?

CVE-2026-105746 is a low-severity vulnerability in docling-project docling, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.83.0 until 2.131.0, the KServeV2OcrModel class defined in docling/models/stages/ocr/kserve_v2_ocr_model.py sends page images to its configured endpoint without checking the pipeline_options.enable_remote_services setting, even when the caller sets that policy control to false. The StandardPdfPipeline._make_ocr_model method also fails to pass the flag into the OCR factory, allowing remote OCR processing in configurations that rely on remote services being disabled. The destination is configured by the caller rather than selected by an attacker. This issue is fixed in 2.131.0.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-668 (Exposure of Resource to Wrong Sphere)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docling` | PyPI | From 2.83.0 | 2.131.0 |

Products: Docling Docling.

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

Upgrade docling to 2.131.0 or later.

## Is CVE-2026-105746 being exploited?

There is no known exploitation of CVE-2026-105746 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-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-105746 and fix it if it is affected.

What it is: CVE-2026-105746 is a low-severity vulnerability in docling-project docling, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105746 in the wild and no public exploit code.

Affected packages and fixed versions:
- docling (PyPI): affected from 2.83.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-105746/ (Markdown: https://insights.sbomify.com/CVE-2026-105746/index.md)
```

## Sources

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

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