CVE-2026-105743: Docling Remote Code Execution Vulnerability
MODERATECVE-2026-105743 is a MODERATE (CVSS 4.0) remote code execution vulnerability (CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition) affecting Docling libraries in the PyPI ecosystem. The issue involves docling has ssrf guard bypass in remote resource fetching (dns rebinding / multi-record resolution; no ip validation in html render mode). Remediation is available by upgrading affected packages to version 2.132.0.
CVE-2026-105743 at a Glance
Security Impact
CVSS: 4.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N).
How to Fix CVE-2026-105743
To remediate this vulnerability, upgrade all affected Docling dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install docling>=2.132.0
pip install docling-slim>=2.132.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show docling
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-105743, inspect your installed packages using pip:
pip show docling
Analyze the terminal output to locate any version of Docling in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.132.0), your application is affected.
Note: The pip show docling command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition, where the product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. In Docling, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-105743 Affected Docling Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
docling
|
PyPI |
≥ 2.91.0
< 2.132.0
|
2.132.0
|
|
docling-slim
|
PyPI |
≥ 2.92.0
< 2.132.0
|
2.132.0
|
References
Frequently Asked Questions
What is CVE-2026-105743?
Which Docling versions are affected?
What version fixes CVE-2026-105743?
Is docling affected?
Is docling-slim affected?
What is the CVSS score of CVE-2026-105743?
What CWE is associated with CVE-2026-105743?
How can I check PyPI dependencies for CVE-2026-105743?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pc36-qwjq-x68c",
"modified" : "2026-10-07T20:42:19Z",
"published" : "2026-10-07T20:42:19Z",
"aliases" : [ "CVE-2026-105743" ],
"summary" : "Docling has SSRF guard bypass in remote resource fetching (DNS rebinding / multi-record resolution; no IP validation in HTML render mode)",
"details" : "### Summary\n\nWhen remote fetching is enabled (`enable_remote_fetch=True`, together with `fetch_images=True` or HTML `render_page=True`), docling's protection against requests to private and loopback addresses can be bypassed.\n\n- The URL check resolves the host name once, to a single IPv4 address. The HTTP request then resolves it again. A name that returns a public A record together with an internal AAAA record, or one that changes its answer between the two lookups (DNS rebinding), reaches internal addresses.\n- The check and the HTTP request parse the URL differently. With a backslash in the authority, such as `http://127.0.0.1:8080\\@1.1.1.1/x.png`, the check validates `1.1.1.1` while the HTTP client connects to `127.0.0.1:8080`.\n- In HTML browser-rendering mode (`render_page=True`), requests made by the page are allowed for any `http(s)` URL without an IP check.\n\n### Details\n\n- `validate_url_safety` in `docling/backend/utils/image_resource_loader.py` calls `socket.gethostbyname()`, which returns one IPv4 address. It checks that address and then passes the original URL string to `requests`, which parses it again with urllib3 and resolves the name independently through `getaddrinfo`. `urllib.parse` treats a backslash in the authority as part of the host section, while urllib3 ends the authority there, so the two can pick different hosts. This loader is shared by the HTML, Markdown, AsciiDoc, OpenDocument and JATS backends.\n- `docling/backend/html_backend.py` routes browser requests in render mode. When `enable_remote_fetch` is set, it continues any `http(s)` request, including iframes and images, without resolving or checking the destination.\n\nJavaScript is disabled during rendering, so the browser path can only show internal responses passively in the page screenshot. It cannot read them and send them elsewhere.\n\n### Affected configurations\n\n- Affected: callers that enable `enable_remote_fetch` (CLI: `--html-image-fetch remote` or `all`) and process untrusted documents.\n- Not affected: the default configuration (`enable_remote_fetch=False`).\n\nThe main-URL fetch for `DocumentConverter.convert(\"https://...\")` is implemented in docling-core and is tracked there.\n\n### Impact\n\nRequests from the converting host to internal services such as cloud metadata endpoints and loopback services. Response content is exposed only when it decodes as an image or is rendered into the page screenshot.\n\n### Patches\n\nFixed in docling 2.132.0 by [#4420](https://github.com/docling-project/docling/pull/4420). The image loader now resolves the host once, requires every resolved address (IPv4 and IPv6, including IPv4-mapped, 6to4 and NAT64 forms) to be globally routable, and connects to one of the validated addresses, using the same parsed host for the check and the connection. Remote requests made during HTML browser rendering are downloaded by the same loader, and the browser itself stays offline. When a proxy is configured through environment variables, requests go through the proxy, which is then responsible for filtering destinations.\n\n### Workarounds\n\nUpgrade to 2.132.0. For older versions:\n\nKeep `enable_remote_fetch=False` for untrusted documents, or block egress to private, link-local and loopback ranges at the network level.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "docling"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.91.0"
}, {
"fixed" : "2.132.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "PyPI",
"name" : "docling-slim"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.92.0"
}, {
"fixed" : "2.132.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/docling-project/docling/security/advisories/GHSA-pc36-qwjq-x68c"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-105743"
}, {
"type" : "WEB",
"url" : "https://github.com/docling-project/docling/pull/4420"
}, {
"type" : "WEB",
"url" : "https://github.com/docling-project/docling/commit/5e469137f275ffc443306a30d12a3a45bceb80fb"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/docling-project/docling"
}, {
"type" : "WEB",
"url" : "https://github.com/docling-project/docling/releases/tag/v2.132.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-367", "CWE-918" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-07T20:42:19Z",
"nvd_published_at" : "2026-10-05T22:16:57Z"
}
}