CVE-2026-105751
Description
A flaw was found in docling. When parsing OpenDocument files, the backend resolves image reference attributes directly as local filesystem paths without enforcing directory boundaries or URI scheme validation. An attacker could provide a crafted document that causes docling to read arbitrary local files, leading to information disclosure if sensitive files are embedded in the generated output or their existence is revealed.
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.
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.3 | 7.5 | N/A |
| Attack Vector | Local | Network | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | None | None | N/A |
| User Interaction | Required | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | Low | High | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | None | None | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
