CVE-2026-44022: Docling: Potential Path Traversal via LaTeX \includegraphics and \input Commands

Published Jun 3, 2026
·
Updated

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().isrelativeto() 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

Other sources

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.

— MITRE

Affected Software

2 affected componentsFixes available
pip/docling>=2.73.0<2.91.0
2.91.0
Docling Docling Python>=2.73.0<2.91.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/docling to a version that resolves this vulnerability.

    Fixed in 2.91.0
  2. Upgrade

    Upgrade docling to a version that resolves this vulnerability.

    Fixed in 2.91.0
  3. Compensating control

    If you must process LaTeX documents, run Docling in a sandboxed environment with restricted file system access.

  4. Compensating control

    Avoid processing untrusted LaTeX documents.

Event History

Jun 3, 2026
Advisory Published
via GitHub·09:14 PM
Data Sourced
via GitHub·09:14 PM
DescriptionSeverityWeaknessAffected Software
Jun 24, 2026
CVE Published
via MITRE·05:47 PM
Data Sourced
via MITRE·05:47 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44022?

The severity of CVE-2026-44022 is classified as medium with a score of 5.5.

2

What is CVE-2026-44022?

CVE-2026-44022 is a vulnerability in the LaTeX backend's handling of certain commands that allows for path traversal, potentially enabling attackers to read arbitrary files.

3

How do I fix CVE-2026-44022?

To fix CVE-2026-44022, update to the latest version of the software that addresses this vulnerability.

4

What software is affected by CVE-2026-44022?

CVE-2026-44022 affects the pip/docling software, specifically within its LaTeX backend.

5

What can attackers achieve with CVE-2026-44022?

Attackers can exploit CVE-2026-44022 to craft malicious LaTeX documents that can read arbitrary files from the file system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203