Is CVE-2026-44520 exploited in the wild?

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

How severe is CVE-2026-44520?

Medium severity, with a CVSS score of 5.7, published 14 May 2026.

Which products and versions are affected?

Docling Project Docling-Graph <= 1.5.0, <=1.5.0; docling-graph (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.1.

Is there a fix for CVE-2026-44520?

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

How is CVE-2026-44520 attacked?

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

Am I affected by CVE-2026-44520?

Check whether you run Docling Project Docling-Graph or docling-graph (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-44520: Docling-Graph SSRF in URLInputHandler

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

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

Q: How is CVE-2026-44520 attacked?

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

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

Check whether you run Docling Project Docling-Graph or docling-graph (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-44520 · Severity: medium · CVSS 5.7 · Published 2026-05-14

docling-graph is a tool used to transform unstructured documents into knowledge graphs. A security vulnerability in how it handles web addresses allows an attacker to force the application to make requests to internal servers or cloud metadata services. This could lead to the theft of sensitive credentials or unauthorized access to internal company data.

Vendors: Docling Project, PyPI.

Quick answers

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

Technical details

The URLInputHandler class in docling_graph/core/input/handlers.py fails to validate whether user-supplied URLs resolve to private, loopback, or link-local IP addresses. The URLValidator only checks for a valid scheme and non-empty netloc, and the use of requests.head() with allow_redirects=True allows attackers to bypass simple checks via redirects. An attacker controlling the --source CLI argument or PipelineConfig.source API parameter can reach internal services or cloud metadata endpoints (e.g., 169.254.169.254) to extract IAM credentials. The vulnerability is fixed in version 1.5.1 by implementing strict IP validation and disabling automatic redirect following.

Affected products

docling-project docling-graph <= 1.5.0

Identifiers

CVE-2026-44520
GHSA-fqph-j6v6-jvgx
PYSEC-2026-2458

Timeline

2026-05-01: disclosed
2026-05-07: advisory: GitHub Advisory published
2026-05-14: other: NVD published

References

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