Is CVE-2026-44019 exploited in the wild?

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

How severe is CVE-2026-44019?

High severity, with a CVSS score of 8.1, published 16 July 2026.

Which products and versions are affected?

docling-core (PyPI) >= 2.5.0, < 2.74.1, ECOSYSTEM:introduced=2.5.0,fixed=2.74.1.

Is there a fix for CVE-2026-44019?

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

How is CVE-2026-44019 attacked?

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

Am I affected by CVE-2026-44019?

Check whether you run docling-core (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-44019: Docling Core local file inclusion and resource exhaustion in image URI handling

Q: Is there a fix for CVE-2026-44019?

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

Q: How is CVE-2026-44019 attacked?

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

Q: Am I affected by CVE-2026-44019?

Check whether you run docling-core (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-44019 · Severity: high · CVSS 8.1 · Published 2026-07-16

Docling Core, a library used for document processing and data transformation, contains a vulnerability in how it handles image references. An attacker could provide a specially crafted document that forces the system to read sensitive local files or crash the application by consuming excessive memory. This could lead to the theft of private data or a disruption of document processing services.

Technologies: docling-core (PyPI). Vendors: PyPI.

Quick answers

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

Technical details

Docling Core versions 2.5.0 through 2.74.0 fail to properly validate image reference URIs, specifically allowing 'file://' schemes and 'data:' URIs without size limits. This vulnerability (CWE-73 and CWE-400) allows a remote attacker to perform local file inclusion (LFI) by referencing files readable by the process or trigger a denial-of-service (DoS) via memory exhaustion from large inline payloads. Exploitation requires the application to process untrusted document input containing these references. The issue is resolved in version 2.74.1, which blocks local file URIs by default and implements decoded-size limits for inline data.

Affected products

docling-project docling-core >= 2.5.0, < 2.74.1

Identifiers

CVE-2026-44019
GHSA-j5xp-7m2f-49jv
PYSEC-2026-2456

Timeline

2026-04-22: patched: Version 2.74.1 released
2026-06-02: advisory: GitHub Security Advisory published
2026-07-16: disclosed: CVE published to NVD

References

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