Live › vulnerability › CVE-2026-47214
Go to dashboardDocling's HTML backend mishandled file:// URIs, relative and absolute paths, internal network addresses and redirects when local or remote fetching was enabled. An attacker who can supply an HTML document can read local files or reach internal network resources through the parser.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| docling | pypi | < 2.94.0 | 2.94.0 |
| docling | vendor | < 2.94.0 | 2.94.0 |
pip show docling and confirm the version is 2.94.0 or later2.94.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
The HTML backend did not perform sufficient validation during resource handling:
file:// URIs enabling local file system access when enable_local_fetch=True../ sequences and absolute pathsenable_remote_fetch=Truedata: URIsFixed in versions 2.91.0 (initial fixes) and 2.94.0 (additional improvements). The fixes implement:
enable_local_fetch=True (default: False) and containment within configured base_path for path traversal protectionfile:// scheme stripped & treated as local path (above)Keep both enable_local_fetch=False and enable_remote_fetch=False (defaults) when processing untrusted HTML documents.
This page as .md · .json · in your agent: get_signal("CVE-2026-47214")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.