Is CVE-2026-44022 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44022 being exploited in the wild.

How severe is CVE-2026-44022?

Medium severity, with a CVSS score of 5.5, published 24 June 2026.

Which products and versions are affected?

docling (PyPI) ECOSYSTEM:introduced=2.73.0,fixed=2.91.0.

Is there a fix for CVE-2026-44022?

Yes. docling (PyPI): upgrade to 2.91.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44022 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-44022?

Check whether you run docling (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44022: Docling path traversal in LaTeX backend

CVE-2026-44022 · Severity: medium · CVSS 5.5 · Published 2026-06-24

Docling is a tool used to convert various document formats into formats compatible with AI systems. A security flaw in its LaTeX processing component allows a malicious document to trick the software into reading sensitive files from the server or computer where it is running. This could lead to the exposure of private data, configuration files, or credentials if an attacker can convince a user or automated system to process a specially crafted LaTeX file.

Technologies: docling (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-44022 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44022 being exploited in the wild.
How severe is CVE-2026-44022?: Medium severity, with a CVSS score of 5.5, published 24 June 2026.
Which products and versions are affected?: docling (PyPI) ECOSYSTEM:introduced=2.73.0,fixed=2.91.0.
Is there a fix for CVE-2026-44022?: Yes. docling (PyPI): upgrade to 2.91.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44022 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-44022?: Check whether you run docling (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

docling (PyPI): upgrade to 2.91.0 or later
```
pip install "docling>=2.91.0"
```

Technical details

A path traversal vulnerability (CWE-22) exists in Docling's LaTeX backend due to insufficient validation of file paths in specific commands. The handling of \includegraphics, \input, and \include commands failed to ensure that resolved paths remained within the intended base directory. An attacker can exploit this by providing a malicious LaTeX document containing path traversal sequences (e.g., ../../../etc/passwd). When processed, the application may include the contents of arbitrary system files in its output. The vulnerability is fixed in version 2.91.0 by implementing strict path validation using Path.resolve().is_relative_to().

Affected products

docling-project Docling >= 2.73.0, < 2.91.0

Identifiers

CVE-2026-44022
GHSA-2j5p-7p5m-cvqr
PYSEC-2026-2145

Timeline

2026-04-23: patched: Version 2.91.0 released
2026-06-02: advisory: GitHub Security Advisory published
2026-06-24: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.