Skip to content

Docling Core: Insufficient validation of image reference URIs

High severity GitHub Reviewed Published Jun 2, 2026 in docling-project/docling-core • Updated Jun 3, 2026

Package

pip docling-core (pip)

Affected versions

>= 2.5.0, < 2.74.1

Patched versions

2.74.1

Description

Impact

In versions >= 2.5.0, < 2.74.1, docling-core could allow local file:// image references and accepted inline data: content without a decoded-size limit.

In applications that accept untrusted image references, this may allow access to local files readable by the process or excessive memory use from large inline payloads.

Patches

Patched in docling-core 2.74.1.
The fix blocks local file URIs by default and adds a size limit for decoded inline image data.

Users should upgrade to:

  • docling-core >= 2.74.1

Workarounds

If upgrading is not immediately possible:

  • reject file: and data: image references from untrusted input
  • allow only approved local or remote image sources
  • apply input size and memory limits to processing workers

References

References

@dolfim-ibm dolfim-ibm published to docling-project/docling-core Jun 2, 2026
Published to the GitHub Advisory Database Jun 3, 2026
Reviewed Jun 3, 2026
Last updated Jun 3, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(13th percentile)

Weaknesses

External Control of File Name or Path

The product allows user input to control or influence paths or file names that are used in filesystem operations. Learn more on MITRE.

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource. Learn more on MITRE.

CVE ID

CVE-2026-44019

GHSA ID

GHSA-j5xp-7m2f-49jv

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.
⚡