Medium severity · published Jun 24, 2026
CVE-2026-44022
Docling: Potential Path Traversal via LaTeX \includegraphics and \input Commands
5.5
CVSS
0.2%
EPSS
No
On KEV
Description
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 vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 11% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
DO
docling · docling-project
>= 2.73.0, < 2.91.0 · source: vendor, NVD
Affected product
DO
docling
docling-project
More from docling
8.8
CVE-2026-105744
Docling: Arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine
8.2
CVE-2026-44016
Docling: Unsafe Playwright-based HTML Rendering
7.8
CVE-2026-105745
Docling: Plugin entry points are imported before the allow_external_plugins check
7.5
CVE-2026-105751
Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend
7.5
CVE-2026-105750
Docling: `enable_local_fetch` is not enforced in HTML browser-rendering mode