Docling: Crafted DoclingDocument JSON embeds local image files into converted output

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-105748: 0.30% estimated exploitation activity in the next 30 days; percentile 23.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary docling accepts serialized DoclingDocument JSON as an input format (InputFormat.JSONDOCLING, enabled by default). A crafted JSON file can set a picture's image uri to a local file path. When the converted document is exported with embedded images (ImageRefMode.EMBEDDED, the CLI default for Markdown and HTML), the referenced file is read and embedded as base64 in the output. Details docling/backend/json/doclingjsonbackend.py validates the JSON into a DoclingDocument without checking image references. The file is then read by docling-core: - DoclingDocument.withembeddedpictures opens file:// and plain-path URIs with PIL. - ImageRef.pilimage checks allowimagefileuri for file:// URIs but not for plain Path values. docling's picture enrichment models load images through this property. Only files that PIL can decode as an image are disclosed. Other files, such as text files or keys, fail to decode and are not embedded. The different error behaviour does reveal whether a path…

Published by the source

7 Oct 2026, 20:41 UTC

Last modified by the source

15 Oct 2026, 14:55 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p944-4xh2-x776

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-p944-4xh2-x776

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-p944-4xh2-x776

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-105748

Advisory: Docling: Crafted DoclingDocument JSON embeds local image files into converted output
IDs: CVE-2026-105748, GHSA-p944-4xh2-x776
Record: https://patchnext.com/advisories/cve-2026-105748 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: docling-slim 2.131.0; docling 2.131.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI docling-slim: affected >= 2.92.0, < 2.131.0; fixed in 2.131.0
- PyPI docling: affected >= 2.16.0, < 2.131.0; fixed in 2.131.0

## Suggested inspection (read-only)
- `python -m pip show docling-slim`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show docling`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on docling-slim, docling.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p944-4xh2-x776 (GitHub-reviewed advisory GHSA-p944-4xh2-x776 lists affected ranges: PyPI docling >=2.16.0 =2.92.0 <2.131.0)
- Verified: https://osv.dev/vulnerability/GHSA-p944-4xh2-x776 (OSV record GHSA-p944-4xh2-x776 lists affected ranges: PyPI docling >=2.16.0 =2.92.0 <2.131.0 (fixed))

Commands are suggestions: review each one before running it.