cve.bz

CVE-2026-105744 docling docling: Path traversal

8.8 highExploit referenceEPSS 0.4%Fix available

High (8.8) in docling docling. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in docling 2.132.0.

On this page
Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.94.0 until 2.132.0, callers that opt into LatexBackendOptions(tikz_engine="tectonic") invoke docling/backend/latex/engines/tectonic.py to compile an untrusted TikZ body and document preamble without restricting TeX file primitives including \openin and \openout. Crafted input can read files available to the converter and create or overwrite writable files, and enabling the tikz_engine_allow_shell_escape option additionally permits shell commands through TeX. The default configuration, which does not enable Tectonic rendering, is not affected. This vulnerability is fixed in 2.132.0.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-73 External Control of File Name or Path
CWE-1188 Initialization of a Resource with an Insecure Default
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105744 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105744?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105744?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105744 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
docling:doclingfrom 2.94.0 before 2.132.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x3q2-h9hx-4r4jPyPIdocling>=2.94.0 <2.132.02.132.0
GHSA-x3q2-h9hx-4r4jPyPIdocling-slim>=2.94.0 <2.132.02.132.0
PYSEC-2026-4191PyPIdocling>=2.94.0 <2.132.02.132.0
PYSEC-2026-4216PyPIdocling-slim>=2.94.0 <2.132.02.132.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

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 and document preamble without restricting TeX file primitives such as \openin and \openout. An attacker who can supply a crafted document for conversion can use these primitives to read files accessible to the converter process and to create or overwrite writable files on the host, impacting confidentiality, integrity, and availability. If the separate tikz_engine_allow_shell_escape option is also enabled, arbitrary command execution through TeX shell escapes is possible. The default docling configuration, which does not enable Tectonic rendering, is not affected. Red Hat rates this flaw moderate, lower than the upstream important rating, because exploitation requires a non-default configuration that explicitly enables the Tectonic engine and requires processing attacker-supplied input, resulting in a local attack vector with high attack complexity and required user interaction rather than the network vector assumed upstream. The affected Red Hat products are tracked as affected and fixes are being pursued through the responsible product teams.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat OpenShift AI 2.25rhoai/odh-feature-server-rhel9:1792148523Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 3.4rhoai/odh-autorag-rhel9:1791557539Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-feature-server-rhel9:1791863220Fixed 2026-10-19RHSA-2026:84734
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Affected
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-sdk-cuda-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-serve-cuda-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105744.

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High
  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON