A bug in Docling’s LaTeX backend allows attackers to embed path‑traversal sequences in \\includegraphics, \\input, or \\include commands. When a malicious LaTeX document is processed, the uninhibited path handling can direct the conversion engine to read and include files that the process can access, exposing configuration files, credentials, or other sensitive information. The flaw is not a denial‑of‑service or code‑execution issue but a direct leak of local files.

The vulnerability affects the Docling product from the docling‑project. Versions 2.73.0 through 2.91.0 lack proper path containment checks. All installations running these releases that accept LaTeX documents from untrusted sources are impacted.

The CVSS score is 5.5, indicating a moderate risk. No EPSS score is available, and the vulnerability is not listed in CISA KEV. Attackers can trigger it by providing crafted LaTeX that specifies out‑of‑container file paths. The impact is limited to the file system accessible to the Docling process; successful exploitation requires the ability to submit or influence the LaTeX input. Given the moderate severity and lack of reported exploitation, the threat remains mainly theoretical but nonetheless significant for any environment that processes untrusted LaTeX.