Path Traversal in docling (CVE-2026-44022)
Summary
Path traversal in docling (CVE-2026-44022). Confidential information can be exposed externally. Mitigation: upgrade to 2.91.0 or later.
Original description
The description as published by the source.
Impact
The LaTeX backend's handling of \includegraphics, \input, and \include commands lacked path containment validation. Attackers could craft malicious LaTeX documents with path traversal sequences (e.g., ../../../etc/passwd) to:
- Read arbitrary files from the file system accessible to the process
- Include sensitive files in the converted document output
- Potentially access configuration files, credentials, or other sensitive data
Patches
Fixed in version 2.91.0. The fix implements strict path validation using Path.resolve().is_relative_to() to ensure all resolved paths remain within the base document directory. Attempts to traverse outside the base directory are logged and blocked.
Workarounds
Avoid processing untrusted LaTeX documents. If processing is necessary, run in a sandboxed environment with restricted file system access.
References
- Fix release: v2.91.0
Source: GitHub Security Advisories (Global) 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-44022 has been found in docling.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade docling to 2.91.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-44022" on the vendor's site.
CVE-2026-44022 (docling) — CWE-22 / CVSS v3 5.5
Attack vector: local / unauthenticated
Patched: 2.91.0 — apply immediately
Workaround: Avoid processing untrusted LaTeX documents.
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.
Path traversal (CWE-22) exists in docling.
Check the vendor advisory for the affected versions of docling.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 2.91.0.
Workaround: Avoid processing untrusted LaTeX documents.
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
-
1Identify exposure identify
grep -r 'docling' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
doclingを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Avoid processing untrusted LaTeX documents.パッチが適用されるまでの応急処置として、Avoid processing untrusted LaTeX documents. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade docling to 2.91.0ステージング環境で 2.91.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com