# CVE-2026-44520: Docling-Graph: SSRF via Missing Internal IP Validation in URLInputHandler

> Attackers can trigger Server-Side Request Forgery by supplying malicious URLs, allowing access to internal network resources.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-fqph-j6v6-jvgx, PYSEC-2026-2458

## What is CVE-2026-44520?

CVE-2026-44520 is a medium-severity server-side request forgery vulnerability in docling-project docling-graph, published on 14 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Docling-Graph turns documents into validated Pydantic objects, then builds a directed knowledge graph with explicit semantic relationships. Prior to 1.5.1, the URLInputHandler class in docling_graph/core/input/handlers.py makes HTTP requests to user-supplied URLs without validating whether the target resolves to a private, loopback, or link-local IP address. The URLValidator only checks for a valid scheme and non-empty netloc, performing no IP-level validation. Additionally, requests.head() was called with allow_redirects=True, allowing an attacker to redirect requests to internal endpoints via an intermediary URL. An attacker who can control the --source CLI argument or PipelineConfig.source API parameter can trigger Server-Side Request Forgery (SSRF). This vulnerability is fixed in 1.5.1.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-44520?

3 open source packages ship an affected version, including docling-graph.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docling-graph` | PyPI | All versions | 1.5.1 |
| `docling-graph` | PyPI | All versions | 1.5.1 |
| `docling-graph` | PyPI | All versions | 1.5.1 |

## How do I fix CVE-2026-44520?

Upgrade docling-graph to 1.5.1 or later.

## Is CVE-2026-44520 being exploited?

There is no known exploitation of CVE-2026-44520 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44520 and fix it if it is affected.

What it is: CVE-2026-44520 is a medium-severity server-side request forgery vulnerability in docling-project docling-graph, published on 14 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-44520 in the wild and no public exploit code.

Affected packages and fixed versions:
- docling-graph (PyPI): affected all versions; fixed in 1.5.1
- docling-graph (PyPI): affected all versions; fixed in 1.5.1
- docling-graph (PyPI): affected all versions; fixed in 1.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44520/ (Markdown: https://insights.sbomify.com/CVE-2026-44520/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44520
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44520
- OSV: https://osv.dev/vulnerability/CVE-2026-44520

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44520/
Summaries are generated and may contain mistakes; the official description above is the record.