Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engineGHSA-x3q2-h9hx-4r4j
HIGHFix: docling-project/docling#4419GHSA-x3q2-h9hx-4r4j is a high-severity (CVSS 7.5) Path Traversal vulnerability in docling. A fix is available for docling — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-x3q2-h9hx-4r4j.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
docling🐍docling-slimReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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\openinread arbitrary files, and their content can be typeset into the rendered picture that ends up in the conversion output. For an in-memoryDocumentStream, staging is skipped entirely.\immediate\openout/\writecreate or overwrite files outside the temporary directory. Neither needs shell escape. Tectonic's--untrustedflag 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 atectonicbinary available (onPATHor in the docling cache), and convert untrusted LaTeX. - Not affected: the default configuration (
tikz_engine=None). docling does not installtectonicautomatically, 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
\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:
TectonicEnginenow defaults toallow_shell_escape=False, and without shell escape Tectonic runs with--untrustedand--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,\XeTeXpicfileor\XeTeXpdffileprimitives, or names an absolute, home, drive-letter or parent-directory path in\input,\include,\includegraphics,\InputIfFileExistsor\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, 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=Truefor untrusted input.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | docling | ≥ 2.94.0&&< 2.132.0 | 2.132.0pip install --upgrade 'docling==2.132.0' |
| 🐍PyPI | docling-slim | ≥ 2.94.0&&< 2.132.0 | 2.132.0pip install --upgrade 'docling-slim==2.132.0' |
Affected Products
doclingdoclingDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for docling, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update docling to 2.132.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x3q2-h9hx-4r4j is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
A moderate severity vulnerability was found in docling, a document conversion library shipped in Red Hat OpenShift AI and Lightspeed Core offerings. When docling is explicitly configured to render LaTeX content with the Tectonic engine (LatexBackendOptions(tikz_engine="tectonic")), it compiles an untrusted TikZ body…
Avoid enabling the Tectonic TikZ engine when processing untrusted LaTeX documents. The default docling configuration does not enable Tectonic rendering and is not affected by this flaw, so deployments that have not opted into LatexBackendOptions(tikz_engine="tectonic") are not exposed. The tikz_engine_allow_shell_escape option, which additionally allows shell command execution through TeX, should not be enabled. For deployments that require Tectonic rendering of untrusted input, no mitigation other than upgrading to a release containing the upstream fix is currently available.Source: Red Hat security advisory for GHSA-x3q2-h9hx-4r4j (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift AI 2.25 | rhoai/odh-feature-server-rhel9:1792148523 | RHSA-2026:87410 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-autorag-rhel9:1791557539 | RHSA-2026:84734 |
Frequently Asked Questions
Is GHSA-x3q2-h9hx-4r4j in your dependencies?
Find it across PyPI, including transitive dependencies.