Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-105744 high CVSS 7.5

Path Traversal in docling (CVE-2026-105744)

Summary

Path traversal in docling (CVE-2026-105744). Successful exploitation can lead to full system takeover. Exploitable via tectonic. Mitigation: upgrade to 2.132.0 or later.

Original description

The description as published by the source.

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…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-105744 has been found in docling.
Attackers can target a specific entry point like tectonic over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade docling to 2.132.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-105744" on the vendor's site.

CVE-2026-105744 (docling) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: tectonic / _resolve_local_dependency / DocumentStream / TectonicEngine
Patched: 2.132.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in docling. Attackers reach the vulnerable code path via tectonic without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of docling. Attack surface: tectonic / _resolve_local_dependency / DocumentStream / TectonicEngine.

🔥 Severity

Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.132.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'docling' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'docling' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で docling を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade docling to 2.132.0

    ステージング環境で 2.132.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip docling
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.132.0"}]}]
pip docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.132.0"}]}]
PyPI docling
[{"type":"ECOSYSTEM","events":[{"introduced":"2.94.0"},{"fixed":"2.132.0"}]}]
PyPI docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"2.94.0"},{"fixed":"2.132.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details