# CVE-2026-105743: Docling has SSRF guard bypass in remote resource fetching (DNS rebinding / multi-record resolution; no IP validation in HTML render mode)

> Attackers can bypass SSRF protections via DNS rebinding to access internal services when remote fetching is enabled in Docling.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-pc36-qwjq-x68c, PYSEC-2026-4190, PYSEC-2026-4214

## What is CVE-2026-105743?

CVE-2026-105743 is a medium-severity server-side request forgery vulnerability in docling-project docling, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, 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.91.0 until 2.132.0, validate_url_safety in docling/backend/utils/image_resource_loader.py validates a hostname with a single IPv4 lookup and then allows the HTTP client to resolve and parse the original URL again, permitting DNS rebinding, mixed public and internal address records, and backslash authority parser disagreement to reach internal services. HTMLBackendOptions(render_page=True) also allows HTTP and HTTPS browser requests without validating their resolved destination. Exploitation requires remote fetching to be enabled, and response content is exposed only when it is decoded as an image or passively rendered in a page screenshot. This issue is fixed in 2.132.0.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

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.91.0 | 2.132.0 |
| `docling` | PyPI | From 2.91.0 | 2.132.0 |
| `docling` | PyPI | From 2.91.0 | 2.132.0 |
| `docling-slim` | PyPI | From 2.92.0 | 2.132.0 |
| `docling-slim` | PyPI | From 2.92.0 | 2.132.0 |
| `docling-slim` | PyPI | From 2.92.0 | 2.132.0 |

Products: Docling Docling.

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

Upgrade docling to 2.132.0 or later.

## Is CVE-2026-105743 being exploited?

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

What it is: CVE-2026-105743 is a medium-severity server-side request forgery vulnerability in docling-project docling, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105743 in the wild and no public exploit code.

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

## Sources

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

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