Skip to main content
Public proof of conceptFix available

CVE-2026-105748

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

A public proof of concept exists; no exploitation attested.

  • Published2026-10-05
  • Fixed in2.131.0
  • WeaknessCWE-200 · CWE-73

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.16.0 until 2.131.0, the InputFormat.JSON_DOCLING backend in docling/backend/json/docling_json_backend.py validates serialized DoclingDocument input without rejecting picture image references that contain local paths or file URIs. When the document is enriched or exported with ImageRefMode.EMBEDDED, the DoclingDocument._with_embedded_pictures and ImageRef.pil_image methods can open those references and place readable image bytes in Markdown or HTML output. Disclosure is limited to files Pillow can decode as images, while differing decode behavior can also reveal whether a path exists. Direct untrusted loading through docling-core is outside this Docling fix. This issue is fixed in 2.131.0.

Timeline

dates in UTC
  1. 2026-10-0522:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-105748?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-105748?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Docling
BranchAffectedFixed in
2.x≥ 2.16.0, < 2.131.02.131.0
2.x≥ 2.92.0, < 2.131.02.131.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-105748 Red Hat Product Security7 known affected

    docling: Docling: Information disclosure via local image file references

    lightspeed-core/rag-tool-cpu-rhel9 as a component of Lightspeed Core · lightspeed-core/rag-tool-cuda-12.9-rhel9 as a component of Lightspeed Core · rhai-early-access/docling-sdk-cuda-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · +4 more

Full record on NVD

Fix

  1. Update Docling to 2.131.0
  2. Workaround from the vendor Red Hat Product Security CVE-2026-105748 · 7 productsThe upstream fix is available in docling 2.131.0, where the JSON_DOCLING backend drops image references that point at local files and logs a warning. For versions that cannot yet be upgraded, the upstream project documents these workarounds when processing untrusted input: remove InputFormat.JSON_D…
  3. No fix available, says the vendor Red Hat Product Security CVE-2026-105748 · 7 productsFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2026-10-06
  • OpenCVESSVC decisionpoc—
  • CNACVSS 3.14.3read 2026-10-23
  • CNAweakness (CWE)CWE-200, CWE-73read 2026-10-23
  • FIRST EPSSEPSS score0.2 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Published
2026-10-05
Last Modified
2026-10-07
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-105748?

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.16.0 until 2.131.0, the InputFormat.JSON_DOCLING backend in docling/backend/json/docling_json_backend.py validates serialized DoclingDocument input without rejecting picture image references that contain local paths or file URIs. When the document is enriched or exported with ImageRefMode.EMBEDDED, the DoclingDocument._with_embedded_pictures and ImageRef.pil_image methods can open those references and place readable image bytes in Markdown or HTML output. Disclosure is limited to files Pillow can decode as images, while differing decode behavior can also reveal whether a path exists. Direct untrusted loading through docling-core is outside this Docling fix. This issue is fixed in 2.131.0.

Is CVE-2026-105748 actively exploited?

A proof-of-concept exploit exists for CVE-2026-105748, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-105748?

CVE-2026-105748 has a CVSS v3 base score of 4.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N.

Running docling? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database