---
id: CVE-2026-44023
aliases:
  - GHSA-jmmv-h3mp-59v8
  - PYSEC-2026-2457
title: 'Docling Core: Unsafe remote filename resolution'
summary: 'Docling Core: Unsafe remote filename resolution'
severity: high
cvss: 8.6
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L'
vendor: docling-core
product: docling-core
ecosystem: pip
affected:
  - 'docling-core >= 1.5.0, < 2.74.1'
patched:
  - docling-core 2.74.1
published: '2026-06-03'
updated: '2026-07-13'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-jmmv-h3mp-59v8'
references:
  - url: >-
      https://github.com/docling-project/docling-core/security/advisories/GHSA-jmmv-h3mp-59v8
  - url: 'https://github.com/docling-project/docling-core'
  - url: 'https://github.com/docling-project/docling-core/releases/tag/v2.74.1'
tags:
  - osv
  - pip
ingestedAt: '2026-07-13T18:57:59.844Z'
epss: 0.00427
epssPercentile: 0.34352
---

## Overview

### 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`](https://github.com/docling-project/docling-core/releases/tag/v2.74.1)

## Affected packages

- `docling-core >= 1.5.0, < 2.74.1`

## Remediation

Upgrade to a patched release:

- `docling-core 2.74.1`