CVE-2026-44022: medium-severity vulnerability in docling-project docling
Docling: Potential Path Traversal via LaTeX \includegraphics and \input Commands
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.5epss 0.2%
Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.73.0 until 2.91.0, he LaTeX backend's handling of \includegraphics, \input, and \include commands lacked path containment validation. Attackers could craft malicious LaTeX documents with path traversal sequences to read arbitrary files from the file system accessible to the process, include sensitive files in the converted document output, or potentially access configuration files, credentials, or other sensitive data This vulnerability is fixed in 2.91.0.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Affected products
docling-project · doclingRelated CVEs — docling-project docling
In the same product, most dangerous first.
CVE-2026-44017HIGHDocling: Unsafe Zip Extraction in EasyOCR Model DownloadEPSS 0.7%CVE-2026-44020HIGHDocling: Unsafe XML Entity Expansion in USPTO Patent BackendEPSS 0.6%CVE-2026-44016HIGHDocling: Unsafe Playwright-based HTML RenderingEPSS 0.6%CVE-2026-105751MEDIUMDocling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backendEPSS 0.4%CVE-2026-105750MEDIUMDocling: `enable_local_fetch` is not enforced in HTML browser-rendering modeEPSS 0.4%CVE-2026-47214HIGHDocling: Unsafe URI and Path Handling in HTML BackendEPSS 0.4%