Is CVE-2026-44023 exploited in the wild?

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

How severe is CVE-2026-44023?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-44023?

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-44023 attacked?

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

Am I affected by CVE-2026-44023?

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-44023: Docling Core SSRF and path traversal in remote filename resolution

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

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-44023 attacked?

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

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

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-44023 · Severity: high · CVSS 8.6 · Published 2026-07-16

Docling Core, a library used for document processing and data transformation, contains a security flaw in how it handles remote file requests. An attacker could provide a malicious web link that tricks the system into accessing or overwriting sensitive local files on the server instead of the intended document. This could lead to the exposure of private data or disruption of the document processing service.

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

Quick answers

Is CVE-2026-44023 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44023 being exploited in the wild.
How severe is CVE-2026-44023?: High severity, with a CVSS score of 8.6, published 16 July 2026.
Which products and versions are affected?: docling-core (PyPI) >= 1.5.0, < 2.74.1, ECOSYSTEM:introduced=1.5.0,fixed=2.74.1.
Is there a fix for CVE-2026-44023?: 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-44023 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-44023?: 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 1.5.0 through 2.74.0 are vulnerable to a combination of Server-Side Request Forgery (SSRF) and Path Traversal (CWE-22). The library fails to sufficiently restrict remote request destinations and unsafely resolves server-provided 'Content-Disposition' headers to local file paths. An attacker can exploit this by providing a crafted URL that, when processed, allows the resolution of filenames outside the intended user-defined cache directory. This can result in unauthorized reading of local files (Confidentiality: High) and limited modification or service impact (Integrity/Availability: Low). The issue is fixed in version 2.74.1, which implements stricter validation and filename normalization.

Affected products

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

Identifiers

CVE-2026-44023
GHSA-jmmv-h3mp-59v8
PYSEC-2026-2457

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.