Is CVE-2026-44020 exploited in the wild?

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

How severe is CVE-2026-44020?

High severity, with a CVSS score of 7.5, published 24 June 2026.

Which products and versions are affected?

docling (PyPI) ECOSYSTEM:introduced=2.13.0,fixed=2.74.0.

Is there a fix for CVE-2026-44020?

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

How is CVE-2026-44020 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-44020?

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-44020: Docling XXE vulnerability in USPTO patent XML parsers

CVE-2026-44020 · Severity: high · CVSS 7.5 · Published 2026-06-24

Docling, a tool used for processing and converting various document formats for AI applications, contains a security flaw in how it handles USPTO patent files. An attacker could provide a specially crafted patent document that, when processed, allows them to read sensitive files from the server, trigger internal network requests, or crash the system. This could lead to data theft or significant service disruptions for organizations using Docling to automate document analysis.

Technologies: docling (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-44020 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44020 being exploited in the wild.
How severe is CVE-2026-44020?: High severity, with a CVSS score of 7.5, published 24 June 2026.
Which products and versions are affected?: docling (PyPI) ECOSYSTEM:introduced=2.13.0,fixed=2.74.0.
Is there a fix for CVE-2026-44020?: Yes. docling (PyPI): upgrade to 2.74.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44020 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-44020?: 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.74.0 or later
```
pip install "docling>=2.74.0"
```

Technical details

Docling versions 2.13.0 through 2.73.x are vulnerable to XML External Entity (XXE) attacks within the USPTO patent XML parsers (ICE v4.x, Grant v2.5, and Application v1.x). The vulnerability stems from the use of the standard 'xml.sax.parseString()' function without disabling external entity resolution. A remote, unauthenticated attacker can exploit this by submitting a malicious XML file containing external entity references or recursive entity expansions (Billion Laughs attack). Successful exploitation can result in the disclosure of local files, Server-Side Request Forgery (SSRF), or a Denial of Service (DoS) via resource exhaustion. The issue is resolved in version 2.74.0 by migrating to 'defusedxml.sax.make_parser()' with secure configurations.

Affected products

docling-project Docling >= 2.13.0, < 2.74.0

Identifiers

CVE-2026-44020
GHSA-m88r-rg27-5xfg
PYSEC-2026-240

Timeline

2026-06-02: advisory: GitHub Security Advisory published
2026-06-24: disclosed: CVE-2026-44020 published to NVD
2026-06-24: patched: Fixed in version 2.74.0

References

https://github.com/docling-project/docling/security/advisories/GHSA-m88r-rg27-5xfg

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