# CVE-2026-44023: Docling Core has unsafe remote filename resolution

> Attackers can exploit unsafe remote filename resolution to perform SSRF attacks and access local files outside the cache directory.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-jmmv-h3mp-59v8, PYSEC-2026-2457

## What is CVE-2026-44023?

CVE-2026-44023 is a high-severity server-side request forgery vulnerability in docling-project docling-core, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Docling Core defines core data types and transformations for the document processing application Docling. In versions 1.5.0 and above, prior to 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner. In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory. This issue has been fixed in version 2.74.1.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including docling-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docling-core` | PyPI | From 1.5.0 | 2.74.1 |
| `docling-core` | PyPI | From 1.5.0 | 2.74.1 |
| `docling-core` | PyPI | From 1.5.0 | 2.74.1 |

Products: Docling Docling-Core.

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

Upgrade docling-core to 2.74.1 or later.

## Is CVE-2026-44023 being exploited?

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

## Other vulnerabilities in docling-project docling-core

- [CVE-2026-24009](https://insights.sbomify.com/CVE-2026-24009/): Docling Core vulnerable to Remote Code Execution via unsafe PyYAML usage (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44023 is a high-severity server-side request forgery vulnerability in docling-project docling-core, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44023 in the wild and no public exploit code.

Affected packages and fixed versions:
- docling-core (PyPI): affected from 1.5.0; fixed in 2.74.1
- docling-core (PyPI): affected from 1.5.0; fixed in 2.74.1
- docling-core (PyPI): affected from 1.5.0; fixed in 2.74.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-44023/ (Markdown: https://insights.sbomify.com/CVE-2026-44023/index.md)
```

## Sources

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

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