CVE-2026-105750: Docling Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-q43m-vhcp-mhvm
CVSS 5.9
CWE-552 CWE-863
Published
Advisory Summary

CVE-2026-105750 is a MODERATE (CVSS 5.9) remote code execution vulnerability (CWE-552: Files or Directories Accessible to External Parties) affecting Docling libraries in the PyPI ecosystem. The issue involves `enable_local_fetch` is not enforced in html browser-rendering mode. Remediation is available by upgrading affected packages to version 2.118.1.

CVE-2026-105750 at a Glance

CVE Identifier CVE-2026-105750
GHSA Identifier GHSA-q43m-vhcp-mhvm
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-552: Files or Directories Accessible to External Parties
Affected Product Docling
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 5.9

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:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-105750

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.

docling fixed: 2.118.1
pip install docling>=2.118.1
docling-slim fixed: 2.118.1
pip install docling-slim>=2.118.1
Verify Direct and Transitive Dependencies

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-105750, 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.118.1), 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-552: Files or Directories Accessible to External Parties, where the product makes files or directories accessible to unauthorized actors, even though they should not be. 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

### Summary When the HTML backend renders pages in a headless browser (`HTMLBackendOptions(render_page=True)`), the `enable_local_fetch` option is not enforced. A crafted HTML file can embed an arbitrary local file (for example with `<iframe src="file:///...">`), and that file's contents appear in the page image attached to the returned `DoclingDocument`. ### Details In render mode, Playwright requests are filtered by `HTMLDocumentBackend._get_browser_request_block_reason`. In affected versions, this check allowed `file:` URLs unconditionally, before reading any option. As a result: - `enable_local_fetch=False` did not block local file access, and - even with `enable_local_fetch=True`, file access was not limited to the source document's directory, unlike the non-render path (`ImageResourceLoader`), which rejects absolute paths and path traversal. Versions 2.82.0–2.90.x did no request filtering in render mode at all. The browser runs with JavaScript disabled (from 2.91.0), so disclosure is passive: only what Chromium renders visibly inside the page viewport ends up in the page image. Only `Path` inputs are affected. They are loaded through a `file://` URL. Stream inputs are loaded with `page.set_content()` into an opaque origin, from which Chromium does not load `file://` subresources. ### Impact An attacker who can submit HTML for conversion can read any text file the conversion process can read (for example `.env` files, credential files, or other users' documents on a shared host) by having it rendered into the page image. Only applications that meet **all** of these conditions are affected: - they set `HTMLBackendOptions(render_page=True)` in Python, - they have the optional `playwright` dependency installed, and - they pass untrusted HTML as a filesystem `Path`. The following are **not** affected: the default configuration (`render_page=False`), the `docling` CLI, `docling-serve`, and the EPUB, Markdown, XBRL and email backends. ### Patches Fixed in **2.118.1** (#3948). In render mode, `file:` requests are now blocked unless `enable_local_fetch=True`, and allowed requests are limited to the source document's directory. ### Workarounds If you can't upgrade, don't use `render_page=True` on untrusted HTML, or pass the input as a stream instead of a `Path`. ### Credits Reported by @priyankn.

CVE-2026-105750 Affected Docling Versions

2 component(s)
Fixed Versions:
2.118.1
Product / Package Ecosystem Affected Versions Fixed Version
docling
PyPI
≥ 2.82.0
< 2.118.1
2.118.1
docling-slim
PyPI
≥ 2.92.0
< 2.118.1
2.118.1

References

Frequently Asked Questions

What is CVE-2026-105750?
CVE-2026-105750 is a security vulnerability in Docling involving `enable_local_fetch` is not enforced in HTML browser-rendering mode under CWE-552: Files or Directories Accessible to External Parties.
Which Docling versions are affected?
Affected versions include releases prior to 2.118.1 across affected packages: docling, docling-slim.
What version fixes CVE-2026-105750?
Upgrading to 2.118.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is docling affected?
Yes, docling is affected in releases prior to 2.118.1. Upgrade your dependency to 2.118.1 or later.
Is docling-slim affected?
Yes, docling-slim is affected in releases prior to 2.118.1. Upgrade your dependency to 2.118.1 or later.
What is the CVSS score of CVE-2026-105750?
CVE-2026-105750 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-105750?
CVE-2026-105750 is classified under CWE-552: Files or Directories Accessible to External Parties (The product makes files or directories accessible to unauthorized actors, even though they should not be.).
How can I check PyPI dependencies for CVE-2026-105750?
Run the dependency tree command: 'pip show docling'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q43m-vhcp-mhvm",
  "modified" : "2026-10-06T00:02:27Z",
  "published" : "2026-10-06T00:02:27Z",
  "aliases" : [ "CVE-2026-105750" ],
  "summary" : "Docling: `enable_local_fetch` is not enforced in HTML browser-rendering mode",
  "details" : "### Summary\n\nWhen the HTML backend renders pages in a headless browser (`HTMLBackendOptions(render_page=True)`), the `enable_local_fetch` option is not enforced. A crafted HTML file can embed an arbitrary local file (for example with `<iframe src=\"file:///...\">`), and that file's contents appear in the page image attached to the returned `DoclingDocument`.\n\n### Details\n\nIn render mode, Playwright requests are filtered by `HTMLDocumentBackend._get_browser_request_block_reason`. In affected versions, this check allowed `file:` URLs unconditionally, before reading any option. As a result:\n\n- `enable_local_fetch=False` did not block local file access, and\n- even with `enable_local_fetch=True`, file access was not limited to the source document's directory, unlike the non-render path (`ImageResourceLoader`), which rejects absolute paths and path traversal.\n\nVersions 2.82.0–2.90.x did no request filtering in render mode at all.\n\nThe browser runs with JavaScript disabled (from 2.91.0), so disclosure is passive: only what Chromium renders visibly inside the page viewport ends up in the page image.\n\nOnly `Path` inputs are affected. They are loaded through a `file://` URL. Stream inputs are loaded with `page.set_content()` into an opaque origin, from which Chromium does not load `file://` subresources.\n\n### Impact\n\nAn attacker who can submit HTML for conversion can read any text file the conversion process can read (for example `.env` files, credential files, or other users' documents on a shared host) by having it rendered into the page image.\n\nOnly applications that meet **all** of these conditions are affected:\n\n- they set `HTMLBackendOptions(render_page=True)` in Python,\n- they have the optional `playwright` dependency installed, and\n- they pass untrusted HTML as a filesystem `Path`.\n\nThe following are **not** affected: the default configuration (`render_page=False`), the `docling` CLI, `docling-serve`, and the EPUB, Markdown, XBRL and email backends.\n\n### Patches\n\nFixed in **2.118.1** (#3948). In render mode, `file:` requests are now blocked unless `enable_local_fetch=True`, and allowed requests are limited to the source document's directory.\n\n### Workarounds\n\nIf you can't upgrade, don't use `render_page=True` on untrusted HTML, or pass the input as a stream instead of a `Path`.\n\n### Credits\n\nReported by @priyankn.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "docling"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.82.0"
      }, {
        "fixed" : "2.118.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "docling-slim"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.92.0"
      }, {
        "fixed" : "2.118.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/security/advisories/GHSA-q43m-vhcp-mhvm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/pull/3948"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/commit/1612b8875b0937447ce3122536fb5360a7102a0a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/docling-project/docling"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/releases/tag/v2.118.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-552", "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-06T00:02:27Z",
    "nvd_published_at" : null
  }
}