CVE-2026-47214: Docling: Unsafe URI and Path Handling in HTML Backend

Published Jun 3, 2026
·
Updated

Impact The HTML backend did not perform sufficient validation during resource handling: - Accepted file:// URIs enabling local file system access when enablelocalfetch=True - Path resolution allowed traversal outside intended directories via ../ sequences and absolute paths - Did not block internal network resources under enableremotefetch=True - HTTP redirects were not validated, potentially redirecting to unintended schemes - No resource limits for remote image downloads and data: URIs

Patches Fixed in versions 2.91.0 (initial fixes) and 2.94.0 (additional improvements). The fixes implement: - Updated local path treatment: absolute files always blocked, relative paths require enablelocalfetch=True (default: False) and containment within configured basepath for path traversal protection - file:// scheme stripped & treated as local path (above) - IP address validation to prevent SSRF - HTTP redirect validation, connection and read timeouts - Size limit for both remote images (with streaming download) and base64-decoded data URIs

Workarounds Keep both enablelocalfetch=False and enableremotefetch=False (defaults) when processing untrusted HTML documents.

References - Initial fixes: v2.91.0 - Additional improvements: v2.94.0

Other sources

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. Prior to 2.94.0, the HTML backend has unsafe URI and path handling. This vulnerability is fixed in 2.94.0.

— MITRE

Affected Software

2 affected componentsFixes available
pip/docling<2.94.0
2.94.0
Docling Docling Python<2.94.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/docling to a version that resolves this vulnerability.

    Fixed in 2.94.0
  2. Upgrade

    Upgrade docling to a version that resolves this vulnerability.

    Fixed in 2.91.0
  3. Upgrade

    Upgrade docling to a version that resolves this vulnerability.

    Fixed in 2.94.0
  4. Configuration

    Keep enable_local_fetch=False (default) when processing untrusted HTML documents to prevent accepted file:// URIs enabling local file system access.

    Docling HTML backend enable_local_fetch = False
  5. Configuration

    Keep enable_remote_fetch=False (default) when processing untrusted HTML documents to avoid remote resource fetching that was insufficiently controlled prior to 2.94.0.

    Docling HTML backend enable_remote_fetch = False

Event History

Jun 3, 2026
Advisory Published
via GitHub·09:15 PM
Data Sourced
via GitHub·09:15 PM
DescriptionSeverityWeaknessAffected Software
Jun 26, 2026
CVE Published
via MITRE·03:45 PM
Data Sourced
via MITRE·03:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-47214?

The severity of CVE-2026-47214 is rated as high with a score of 7.1.

2

What vulnerabilities are associated with CVE-2026-47214?

CVE-2026-47214 is associated with Path Traversal and Server-Side Request Forgery (SSRF) vulnerabilities.

3

How do I fix CVE-2026-47214?

To fix CVE-2026-47214, update to the latest version of the affected software as released by the maintainers in subsequent updates.

4

What impact does CVE-2026-47214 have on my system?

CVE-2026-47214 can lead to unauthorized local file system access and directory traversal, potentially exposing sensitive files.

5

Which software is affected by CVE-2026-47214?

CVE-2026-47214 affects the pip and docling software.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203