Skip to content

Docling: Potential Path Traversal via LaTeX \includegraphics and \input Commands

Moderate severity GitHub Reviewed Published Jun 2, 2026 in docling-project/docling

Package

pip docling (pip)

Affected versions

>= 2.73.0, < 2.91.0

Patched versions

2.91.0

Description

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

References

@dolfim-ibm dolfim-ibm published to docling-project/docling Jun 2, 2026
Published to the GitHub Advisory Database Jun 3, 2026
Reviewed Jun 3, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(6th percentile)

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Learn more on MITRE.

CVE ID

CVE-2026-44022

GHSA ID

GHSA-2j5p-7p5m-cvqr

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.