Is CVE-2026-47214 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47214 being exploited in the wild.

How severe is CVE-2026-47214?

High severity, with a CVSS score of 7.1, published 26 June 2026.

Which products and versions are affected?

docling (PyPI) ECOSYSTEM:introduced=0,fixed=2.94.0.

Is there a fix for CVE-2026-47214?

Yes. docling (PyPI): upgrade to 2.94.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47214 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47214?

Check whether you run docling (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47214: Docling unsafe URI and path handling in HTML backend

CVE-2026-47214 · Severity: high · CVSS 7.1 · Published 2026-06-26

Docling, a tool used to convert and process documents for AI applications, contains a vulnerability in how it handles HTML files. An attacker could provide a specially crafted document that tricks the system into accessing private local files or internal network resources. This could lead to the exposure of sensitive data or cause the system to slow down by consuming excessive resources.

Technologies: docling (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-47214 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47214 being exploited in the wild.
How severe is CVE-2026-47214?: High severity, with a CVSS score of 7.1, published 26 June 2026.
Which products and versions are affected?: docling (PyPI) ECOSYSTEM:introduced=0,fixed=2.94.0.
Is there a fix for CVE-2026-47214?: Yes. docling (PyPI): upgrade to 2.94.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47214 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47214?: Check whether you run docling (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

docling (PyPI): upgrade to 2.94.0 or later
```
pip install "docling>=2.94.0"
```

Technical details

The Docling HTML backend fails to properly validate resource URIs and file paths during document processing. Specifically, the library allowed 'file://' URIs and path traversal sequences (../), enabling unauthorized access to the local file system when 'enable_local_fetch' was active. Additionally, the backend lacked validation for internal network resources and HTTP redirects, creating a Server-Side Request Forgery (SSRF) risk. The vulnerability also includes a lack of resource limits for remote image downloads and data URIs, which can lead to uncontrolled resource consumption. These issues are addressed in version 2.94.0 by implementing IP validation, redirect checks, size limits, and stricter path containment.

Affected products

docling-project docling < 2.94.0

Identifiers

CVE-2026-47214
GHSA-q29v-xc37-wh5m
PYSEC-2026-2146

Timeline

2026-06-02: advisory: GitHub security advisory published
2026-05-18: patched: Version 2.94.0 released
2026-06-26: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.