CVE-2026-105750 docling-project CVE debrief

Who should care

Defenders responsible for Docling deployments, especially those using the HTML backend in render mode, should assess their exposure and verify the impact of the `enable_local_fetch` option not being enforced.

Why it matters

The vulnerability in Docling's HTML browser-rendering mode allows for potential exposure of sensitive local files and unauthorized local file access. Defenders should prioritize verifying exposure, reviewing and adjusting `enable_local_fetch` settings, and monitoring for potential local file access attempts.

• Potential exposure of sensitive local files
• Risk of unauthorized local file access
• Need for verification of Docling version and configuration
• Potential impact on data confidentiality

Technical summary

The Docling library does not enforce the `enable_local_fetch` option when rendering pages in a headless browser. This allows crafted HTML files to embed arbitrary local files, potentially exposing sensitive information. The vulnerability affects the HTML backend in render mode, allowing file access beyond the source document's directory. Defenders should prioritize verifying exposure in Docling deployments, especially those using the HTML backend in render mode, and assess the impact of the `enable_local_fetch` option not being enforced.

Defensive priority

Defenders should prioritize verifying exposure in Docling deployments, especially those using the HTML backend in render mode, and assess the impact of the `enable_local_fetch` option not being enforced.

Recommended defensive actions

• Verify Docling version and assess exposure
• Review and adjust `enable_local_fetch` settings
• Monitor for potential local file access attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including its impact on the Docling library when rendering pages in a headless browser. Evidence is based on official CVE and source item records.

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.