CVE-2026-105751 docling-project CVE debrief

Who should care

Defenders responsible for systems and deployments that use Docling, especially those processing untrusted .odt files, should assess exposure and prioritize verification and updates.

Why it matters

CVE-2026-105751 allows an attacker to read arbitrary local files by crafting a malicious .odt file, potentially leading to unauthorized file disclosure and elevation of privileges. Defenders should prioritize verification and updates, and assess exposure in their environments.

• Potential unauthorized local file disclosure
• Possible elevation of privileges through file system access
• Required verification of file handling and validation mechanisms
• Need for secure update and patch management for Docling

Technical summary

The ODF backend in Docling resolves the xlink:href of a draw:image element as a filesystem path, allowing an attacker to read arbitrary local files by crafting a malicious .odt file. The affected component is `docling/backend/opendocument_backend.py`, in `_image_ref_from_odf_image`. The vulnerability is triggered by a 452-byte archive containing two entries. Converters should verify and update Docling to version 2.120.3 or later. The vulnerability allows an attacker to read arbitrary local files, potentially leading to unauthorized file disclosure and elevation of privileges.

Defensive priority

Defenders should prioritize verifying and updating Docling to version 2.120.3 or later, and assess exposure in their environments, especially where untrusted .odt files are processed.

Recommended defensive actions

• Verify and update Docling to version 2.120.3 or later
• Assess exposure in environments where untrusted .odt files are processed
• Implement secure file handling and validation for .odt files
• Monitor for suspicious activity related to Docling
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the vulnerability, including the affected component, attack vector, and fixed version. However, some details, such as the CVSS score and severity, are not provided.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.