Products / docling
docling
17 records.
- Docling imports plugin entry points before the allow_external_plugins check Docling imports every installed plugin module before applying the external-plugin restriction, so third-party import-time code runs even when external plugins are disabled.
- Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion A tiny HTML or spreadsheet file with huge span attributes makes the converter loop and allocate oversized tables, exhausting CPU and memory.
- Docling: Configured HTTP headers sent to every remote image host named by a document
- Docling: Crafted DoclingDocument JSON embeds local image files into converted output
- Docling has SSRF guard bypass in remote resource fetching (DNS rebinding / multi-record resolution; no IP validation in HTML render mode)
- Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine
- Docling: METS-GBS archive member limit enforced after full member enumeration (memory exhaustion during format detection) Tar archives have all member headers enumerated into memory before the member-count limit applies, so many empty entries exhaust memory.
- Docling: `enable_local_fetch` is not enforced in HTML browser-rendering mode
- Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend A crafted ODF file makes the backend read an absolute path named in an image reference, embedding the file contents in the converted output.
- Docling: Potential Path Traversal via LaTeX \includegraphics and \input Commands The LaTeX converter follows include and graphics paths without checking they stay inside the document directory, so traversal reads files outside it.
- Docling: Unsafe Zip Extraction in EasyOCR Model Download Model archive extraction does not check member paths, so a crafted zip from a compromised download source can write files anywhere the process can write.
- Docling: Unsafe XML Entity Expansion in USPTO Patent Backend
- Docling: Unsafe Playwright-based HTML Rendering
- Docling: Unsafe URI and Path Handling in HTML Backend
- Docling: Unsafe Archive Extraction and XML Parsing in METS-GBS Backend
- Docling's METS GBS backend is vulnerable to XML Entity Expansion (XXE) attacks Crafted XML inside a tar.gz archive triggers exponential entity expansion during parsing because entity resolution is not disabled, exhausting resources.
- Docling's JATS XML backend is vulnerable to XML Entity Expansion (XXE) attacks The JATS XML parser resolves entities without limits, so a nested entity payload expands exponentially and exhausts resources.