Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-105744: 0.37% estimated exploitation activity in the next 30 days; percentile 30.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary When the LaTeX backend is configured to render TikZ pictures with the Tectonic engine (LatexBackendOptions(tikzengine="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 tikzengineallowshellescape=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. resolvelocaldependency 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…

Published by the source

7 Oct 2026, 20:42 UTC

Last modified by the source

15 Oct 2026, 14:55 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x3q2-h9hx-4r4j

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-x3q2-h9hx-4r4j

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-x3q2-h9hx-4r4j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-105744

Advisory: Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine
IDs: CVE-2026-105744, GHSA-x3q2-h9hx-4r4j
Record: https://patchnext.com/advisories/cve-2026-105744 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: docling-slim 2.132.0; docling 2.132.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI docling-slim: affected >= 2.94.0, < 2.132.0; fixed in 2.132.0
- PyPI docling: affected >= 2.94.0, < 2.132.0; fixed in 2.132.0

## Suggested inspection (read-only)
- `python -m pip show docling-slim`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show docling`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on docling-slim, docling.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x3q2-h9hx-4r4j (GitHub-reviewed advisory GHSA-x3q2-h9hx-4r4j lists affected ranges: PyPI docling >=2.94.0 =2.94.0 <2.132.0)
- Verified: https://osv.dev/vulnerability/GHSA-x3q2-h9hx-4r4j (OSV record GHSA-x3q2-h9hx-4r4j lists affected ranges: PyPI docling >=2.94.0 =2.94.0 <2.132.0 (fixed))

Commands are suggestions: review each one before running it.