CVE-2026-105744: Docling Docling Has Arbitrary File Read/write Vulnerability

HIGH
Advisory Identifier: GHSA-x3q2-h9hx-4r4j
CVSS 7.5
CWE-1188 CWE-73 CWE-22
Published
Advisory Summary

CVE-2026-105744 is a HIGH (CVSS 7.5) docling has arbitrary file read/write vulnerability (CWE-1188: Initialization of a Resource with an Insecure Default) affecting Docling libraries in the PyPI ecosystem. The issue involves docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted tikz with the opt-in tectonic engine. Remediation is available by upgrading affected packages to version 2.132.0.

CVE-2026-105744 at a Glance

CVE Identifier CVE-2026-105744
GHSA Identifier GHSA-x3q2-h9hx-4r4j
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-1188: Initialization of a Resource with an Insecure Default
Affected Product Docling
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.5

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

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

How to Fix CVE-2026-105744

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.132.0
pip install docling>=2.132.0
docling-slim fixed: 2.132.0
pip install docling-slim>=2.132.0
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-105744, 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-1188: Initialization of a Resource with an Insecure Default, where the product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure. 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 LaTeX backend is configured to render TikZ pictures with the Tectonic engine (`LatexBackendOptions(tikz_engine="tectonic")`), the TikZ body and the document preamble from the input file are compiled by Tectonic without any restriction on TeX's file primitives. A crafted `.tex` file can read files the process can read and write files at paths the process can write. If the caller also sets `tikz_engine_allow_shell_escape=True`, the document can run shell commands through `\write18`. ### Details `docling/backend/latex/engines/tectonic.py` writes the picture source into a temporary document and runs the `tectonic` binary on it. `_resolve_local_dependency` only decides which files are staged into the temporary directory. It does not limit what TeX opens at compile time, so: - `\input{/abs/path}`, `\verbatiminput{...}` and `\openin` read arbitrary files, and their content can be typeset into the rendered picture that ends up in the conversion output. For an in-memory `DocumentStream`, staging is skipped entirely. - `\immediate\openout` / `\write` create or overwrite files outside the temporary directory. Neither needs shell escape. Tectonic's `--untrusted` flag does not block them either. Separately, the `TectonicEngine` constructor defaults to `allow_shell_escape=True`. The LaTeX backend always passes `tikz_engine_allow_shell_escape` explicitly (default `False`), so this default only affects code that instantiates `TectonicEngine` directly. ### Affected configurations - Affected: callers that set `tikz_engine="tectonic"`, have a `tectonic` binary available (on `PATH` or in the docling cache), and convert untrusted LaTeX. - Not affected: the default configuration (`tikz_engine=None`). docling does not install `tectonic` automatically, and the CLI exposes no option to enable it. ### Impact Disclosure of local files readable by the process, and creation or overwrite of files writable by the process. Writing to startup or configuration files can lead to code execution. With shell escape enabled, commands run directly. ### Proof of concept ```latex \documentclass{article} \usepackage{tikz} \begin{document} \begin{tikzpicture} \immediate\openout15=/tmp/docling-tectonic-poc.txt \immediate\write15{written by the input document} \immediate\closeout15 \node {x}; \end{tikzpicture} \end{document} ``` Converting this file with `LatexBackendOptions(tikz_engine="tectonic")` creates `/tmp/docling-tectonic-poc.txt`. ### Patches Mitigated in docling 2.132.0 by [#4419](https://github.com/docling-project/docling/pull/4419): - `TectonicEngine` now defaults to `allow_shell_escape=False`, and without shell escape Tectonic runs with `--untrusted` and `--only-cached`. - Before compiling, docling checks the generated document and every staged file. It skips rendering, and keeps the diagram as TikZ code, when the source uses the `\openin`, `\openout`, `\XeTeXpicfile` or `\XeTeXpdffile` primitives, or names an absolute, home, drive-letter or parent-directory path in `\input`, `\include`, `\includegraphics`, `\InputIfFileExists` or `\graphicspath`. This check is best-effort. It reads the source text, and TeX can open files in ways a text check cannot see, for example through package commands or names built by macros. As documented in the [pipeline options reference](https://github.com/docling-project/docling/blob/main/docs/reference/pipeline_options.md), untrusted LaTeX rendered with `tikz_engine="tectonic"` should still be processed in an isolated environment. ### Workarounds Upgrade to 2.132.0. For older versions: - Do not enable `tikz_engine="tectonic"` for untrusted input, or run the conversion in an OS-level sandbox (container, no host mounts, read-only filesystem, no network). - Never set `tikz_engine_allow_shell_escape=True` for untrusted input.

CVE-2026-105744 Affected Docling Versions

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

References

Frequently Asked Questions

What is CVE-2026-105744?
CVE-2026-105744 is a security vulnerability in Docling involving Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine under CWE-1188: Initialization of a Resource with an Insecure Default.
Which Docling versions are affected?
Affected versions include releases prior to 2.132.0 across affected packages: docling, docling-slim.
What version fixes CVE-2026-105744?
Upgrading to 2.132.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is docling affected?
Yes, docling is affected in releases prior to 2.132.0. Upgrade your dependency to 2.132.0 or later.
Is docling-slim affected?
Yes, docling-slim is affected in releases prior to 2.132.0. Upgrade your dependency to 2.132.0 or later.
What is the CVSS score of CVE-2026-105744?
CVE-2026-105744 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-105744?
CVE-2026-105744 is classified under CWE-1188: Initialization of a Resource with an Insecure Default (The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.).
How can I check PyPI dependencies for CVE-2026-105744?
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-x3q2-h9hx-4r4j",
  "modified" : "2026-10-07T20:42:05Z",
  "published" : "2026-10-07T20:42:05Z",
  "aliases" : [ "CVE-2026-105744" ],
  "summary" : "Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine",
  "details" : "### Summary\n\nWhen the LaTeX backend is configured to render TikZ pictures with the Tectonic engine (`LatexBackendOptions(tikz_engine=\"tectonic\")`), the TikZ body and the document preamble from the input file are compiled by Tectonic without any restriction on TeX's file primitives. A crafted `.tex` file can read files the process can read and write files at paths the process can write. If the caller also sets `tikz_engine_allow_shell_escape=True`, the document can run shell commands through `\\write18`.\n\n### Details\n\n`docling/backend/latex/engines/tectonic.py` writes the picture source into a temporary document and runs the `tectonic` binary on it. `_resolve_local_dependency` only decides which files are staged into the temporary directory. It does not limit what TeX opens at compile time, so:\n\n- `\\input{/abs/path}`, `\\verbatiminput{...}` and `\\openin` read arbitrary files, and their content can be typeset into the rendered picture that ends up in the conversion output. For an in-memory `DocumentStream`, staging is skipped entirely.\n- `\\immediate\\openout` / `\\write` create or overwrite files outside the temporary directory. Neither needs shell escape. Tectonic's `--untrusted` flag does not block them either.\n\nSeparately, the `TectonicEngine` constructor defaults to `allow_shell_escape=True`. The LaTeX backend always passes `tikz_engine_allow_shell_escape` explicitly (default `False`), so this default only affects code that instantiates `TectonicEngine` directly.\n\n### Affected configurations\n\n- Affected: callers that set `tikz_engine=\"tectonic\"`, have a `tectonic` binary available (on `PATH` or in the docling cache), and convert untrusted LaTeX.\n- Not affected: the default configuration (`tikz_engine=None`). docling does not install `tectonic` automatically, and the CLI exposes no option to enable it.\n\n### Impact\n\nDisclosure of local files readable by the process, and creation or overwrite of files writable by the process. Writing to startup or configuration files can lead to code execution. With shell escape enabled, commands run directly.\n\n### Proof of concept\n\n```latex\n\\documentclass{article}\n\\usepackage{tikz}\n\\begin{document}\n\\begin{tikzpicture}\n  \\immediate\\openout15=/tmp/docling-tectonic-poc.txt\n  \\immediate\\write15{written by the input document}\n  \\immediate\\closeout15\n  \\node {x};\n\\end{tikzpicture}\n\\end{document}\n```\n\nConverting this file with `LatexBackendOptions(tikz_engine=\"tectonic\")` creates `/tmp/docling-tectonic-poc.txt`.\n\n### Patches\n\nMitigated in docling 2.132.0 by [#4419](https://github.com/docling-project/docling/pull/4419):\n\n- `TectonicEngine` now defaults to `allow_shell_escape=False`, and without shell escape Tectonic runs with `--untrusted` and `--only-cached`.\n- Before compiling, docling checks the generated document and every staged file. It skips rendering, and keeps the diagram as TikZ code, when the source uses the `\\openin`, `\\openout`, `\\XeTeXpicfile` or `\\XeTeXpdffile` primitives, or names an absolute, home, drive-letter or parent-directory path in `\\input`, `\\include`, `\\includegraphics`, `\\InputIfFileExists` or `\\graphicspath`.\n\nThis check is best-effort. It reads the source text, and TeX can open files in ways a text check cannot see, for example through package commands or names built by macros. As documented in the [pipeline options reference](https://github.com/docling-project/docling/blob/main/docs/reference/pipeline_options.md), untrusted LaTeX rendered with `tikz_engine=\"tectonic\"` should still be processed in an isolated environment.\n\n### Workarounds\n\nUpgrade to 2.132.0. For older versions:\n\n- Do not enable `tikz_engine=\"tectonic\"` for untrusted input, or run the conversion in an OS-level sandbox (container, no host mounts, read-only filesystem, no network).\n- Never set `tikz_engine_allow_shell_escape=True` for untrusted input.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "docling"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.94.0"
      }, {
        "fixed" : "2.132.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "docling-slim"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.94.0"
      }, {
        "fixed" : "2.132.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/security/advisories/GHSA-x3q2-h9hx-4r4j"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-105744"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/pull/4419"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/commit/38b6fa0a465d46fdacbbec333f50fa19c4f6b342"
  }, {
    "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-1188", "CWE-22", "CWE-73" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-07T20:42:05Z",
    "nvd_published_at" : "2026-10-05T22:16:57Z"
  }
}