cve.bz

CVE-2026-105751 docling docling: Path traversal

6.9 mediumExploit referenceEPSS 0.4%Fix available

Medium (6.9) in docling docling. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in docling 2.120.3.

On this page
Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.107.0 until 2.120.3, docling/backend/opendocument_backend.py uses the xlink:href attribute value of a draw:image element as a filesystem path when the referenced part is not found in the document archive. The _image_ref_from_odf_image function reads that attacker-controlled path without a scheme check, extraction-directory confinement, or the enable_local_fetch setting used by other backends. Readable files that Pillow can decode as images are embedded in converted output, and other existing paths can be distinguished through the attempted read. This issue is fixed in 2.120.3.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105751 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105751?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105751?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105751 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
docling:doclingfrom 2.107.0 before 2.120.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4xhp-xg4w-8ppmPyPIdocling>=2.107.0 <2.120.32.120.3
PYSEC-2026-4207PyPIdocling>=2.107.0 <2.120.32.120.3

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low impact information disclosure vulnerability was found in the docling document conversion library, which is bundled in Red Hat OpenShift AI and Lightspeed Core container images. When docling parses an OpenDocument file, the OpenDocument backend uses the xlink:href attribute of a draw:image element as a local filesystem path whenever the referenced part is not found in the document archive. That path is read without a URI scheme check, extraction-directory confinement, or the enable_local_fetch guard that other backends apply, so an attacker who supplies a crafted OpenDocument document can cause docling to read arbitrary local files readable by the conversion process. Files that Pillow can decode as images are embedded in the converted output, disclosing their contents, and the attempted read can also reveal whether other local paths exist. Exploitation requires a user or automated workflow to process the attacker-crafted document, and only confidentiality is affected.

Red Hat rates this flaw as LOW severity (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, score 3.3) because exploitation requires user interaction with a crafted document processed locally and the disclosure is limited to image-decodable files and file-existence inference within the permissions of the converting process. The upstream CVSS:4.0 score of 6.9 (MODERATE) is higher because it treats the flaw as network-reachable with high confidentiality impact, which does not reflect how docling is used in Red Hat products.

The affected products are Red Hat OpenShift AI and Lightspeed Core container images that bundle a vulnerable docling release; the rhoai-3.3 stream is out of support scope. Because this flaw is rated LOW impact, the fix is deferred in line with Red Hat Product Security remediation prioritization for low-severity issues. The residual risk is limited to local information disclosure when docling processes untrusted OpenDocument files.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Fix deferred
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-sdk-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-serve-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-autorag-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105751.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON