CVE-2026-105743 docling-project CVE debrief

Who should care

Defenders and administrators of systems using Docling versions 2.91.0 through 2.132.0 should assess exposure and prioritize patching to prevent potential SSRF attacks. This includes reviewing configurations, verifying affected versions, and monitoring for suspicious activity. Security teams and vulnerability management teams should also review and update their security policies and procedures to address this vulnerability.

Why it matters

CVE-2026-105743 is a medium-severity SSRF vulnerability in Docling project versions 2.91.0 to 2.132.0. It allows for DNS rebinding attacks, potentially leading to unauthorized internal service access. Defenders should prioritize patching and review configurations to prevent exploitation.

• Potential unauthorized access to internal services via SSRF
• Bypassing of SSRF protections through DNS rebinding
• Exposure of response content when decoded as an image or rendered in a page screenshot
• Requires verification of affected versions and exposure

Technical summary

The vulnerability exists in the `validate_url_safety` function in `docling/backend/utils/image_resource_loader.py`. It allows DNS rebinding and mixed public and internal address records, enabling access to internal services without proper validation. HTML render mode also lacks IP validation for HTTP and HTTPS requests. This issue is fixed in version 2.132.0. Exploitation requires remote fetching to be enabled, and response content is exposed only when it is decoded as an image or passively rendered in a page screenshot.

Defensive priority

Defenders should prioritize patching to prevent potential SSRF attacks. Given the medium severity, immediate action is recommended but may not be critical depending on the exposure of affected systems.

Recommended defensive actions

• Patch Docling to version 2.132.0 or later
• Review and restrict remote resource fetching configurations
• Monitor for suspicious internal service access attempts
• Verify affected Docling versions and configurations
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• Track exceptions and retest remediated assets

Evidence notes

Evidence from the CVE Program and NVD provides details on the vulnerability, including its existence in versions 2.91.0 through 2.132.0 of Docling. The CVE Program record and NVD detail page offer official assessments and metadata.

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.