Advisory record · GHSA-jmmv-h3mp-59v8

Docling Core: Unsafe remote filename resolution

CVSS 8.6 HighEPSS 0.0043 · 37th percentile

Published by the GitHub Advisory Database at 3 Jun 2026, 21:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
docling-corePyPI>=1.5.0, <2.74.12.74.1
Identifiers
GHSA-jmmv-h3mp-59v8 · CVE-2026-44023 · PYSEC-2026-2457
Weakness (CWE)
CWE-22 · CWE-918
Published
3 Jun 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of docling-core from 1.5.0 up to, but not including, 2.74.1 do not sufficiently restrict remote request destinations and can resolve a server-provided Content-Disposition filename to a local path unsafely. In applications that accept untrusted URLs, an attacker could use this to carry out SSRF attacks that reach local files outside the user-defined cache directory. Upgrade to docling-core 2.74.1 or later; until then, avoid passing untrusted URLs into remote fetch functionality.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0043, the 37th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:59 UTC First seen by agentprime
  2. 31 Oct 2026, 14:59 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.