Technical impact
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, the library did not sufficiently restrict remote request destinations and could resolve a server‑provided Content‑Disposition header to a local path in an unsafe manner. This vulnerability can allow an attacker, via an untrusted URL, to influence the filename used when downloading content, effectively enabling a server‑side request forgery that targets local files outside the user‑defined cache directory. An attempt to read or write files at arbitrary paths that are not intended to be exposed may result in disclosure of sensitive data or integrity compromise. The issue has been fixed in version 2.74.1.
Affected Systems
The vulnerability affects Docling Core from version 1.5.0 up through 2.74.0. All installations of the docling‑project:docling‑core vendor that have not upgraded to version 2.74.1 or newer are susceptible. The affected product is the core library that powers document processing applications built on the Docling framework.
Risk and Exploitability
The CVSS score of 8.6 indicates a high severity impact. The EPSS score of less than 1 % shows that current exploitation attempts are very rare, and the vulnerability is not listed in the CISA KEV catalog. The flaw stems from a file path traversal weakness (CWE‑22) and a server‑side request forgery vulnerability (CWE‑918). The likely attack vector is a Web or command‑line application that accepts arbitrary URLs, using that to trigger a download from a malicious server. A successful exploit would allow an attacker to read local files outside the allowed cache area, leading to potential data disclosure and integrity compromise. Nonetheless, the low EPSS suggests that immediate detection of attack activity would be rare unless the attacker specifically targets vulnerable Docling deployments.
Github GHSA