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

High 8.6 Published Updated

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

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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, CWE-22

Which versions are affected by CVE-2026-44023?

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

PackageAffectedFixed in
docling-core PyPIFrom 1.5.02.74.1
docling-core PyPIFrom 1.5.02.74.1
docling-core PyPIFrom 1.5.02.74.1

Products include Docling Docling-Core.

How do I fix CVE-2026-44023?

Upgrade docling-core to 2.74.1 or later.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-44023 being exploited?

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

Sources

Also known as GHSA-jmmv-h3mp-59v8, PYSEC-2026-2457.

Is CVE-2026-44023 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free