Live › vulnerability › CVE-2026-112310
Go to dashboarddocling-core versions from 2.5.0 before 2.103.0 accept plain filesystem paths in ImageRef URIs, bypassing the allow_image_file_uri check. An attacker who supplies a crafted DoclingDocument JSON or YAML file can get local image files embedded as base64 on export or HTML rendering, which also reveals whether paths exist.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that parse untrusted DoclingDocument JSON or YAML and then export it with embedded images or render it to HTML are exposed, because the crafted file can pull local files into the output. Systems that only process documents they create themselves, or that never export embedded images, are much less exposed. unknown whether the sources list other affected paths.
No product ranges from the sources yet.
pip show docling-core and check whether the version is below 2.103.0.ImageRefMode.EMBEDDED or HTML rendering of documents that come from untrusted users.2.103.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
docling-core 2.5.0 before 2.103.0 contains a local file disclosure vulnerability that allows attackers to read local images by supplying plain filesystem paths in ImageRef URIs, bypassing the allow_image_file_uri gate. Attackers can submit crafted DoclingDocument JSON or YAML that, when exported with ImageRefMode.EMBEDDED or rendered to HTML, embeds readable local image files as base64 and reveals path existence.
This page as .md · .json · in your agent: get_signal("CVE-2026-112310")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.