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

Published Jun 3, 2026
·
Updated

Impact In versions >= 1.5.0, < 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.

Patches Patched in docling-core 2.74.1. The fix adds stricter validation for remote destinations and normalizes server-provided filenames before use.

Users should upgrade to: - docling-core >= 2.74.1

Workarounds If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.

References - Fix release: v2.74.1

Other sources

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.

— MITRE

Affected Software

2 affected componentsFixes available
pip/docling-core>=1.5.0<2.74.1
2.74.1
Docling Docling-core Python>=1.5.0<2.74.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/docling-core to a version that resolves this vulnerability.

    Fixed in 2.74.1
  2. Upgrade

    Upgrade docling-core to a version that resolves this vulnerability.

    Fixed in 2.74.1
  3. Compensating control

    If you cannot upgrade immediately, avoid passing untrusted URLs into the remote fetch functionality in applications using docling-core; this reduces SSRF risk that could target local files outside the user-defined cache directory.

Event History

Jun 3, 2026
Advisory Published
via GitHub·09:16 PM
Data Sourced
via GitHub·09:16 PM
DescriptionSeverityWeaknessAffected Software
Jul 16, 2026
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44023?

The severity of CVE-2026-44023 is rated as high with a score of 8.6.

2

How do I fix CVE-2026-44023?

To fix CVE-2026-44023, upgrade to docling-core version 2.74.1 or later.

3

What types of attacks are associated with CVE-2026-44023?

CVE-2026-44023 is associated with Server-Side Request Forgery (SSRF) attacks due to improper handling of URLs.

4

In which versions of docling-core is CVE-2026-44023 present?

CVE-2026-44023 is present in docling-core versions from 1.5.0 to less than 2.74.1.

5

What impact does CVE-2026-44023 have on applications?

CVE-2026-44023 can potentially allow untrusted URL inputs to perform path traversal and SSRF attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203