Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion
docling-project docling · docling-project docling-slim
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| docling PyPI |
|
|
| docling-slim PyPI |
|
|
docling-project docling · docling-project docling-slim
| Product | Affected | Fixed in |
|---|---|---|
| docling PyPI |
|
|
| docling-slim PyPI |
|
|
Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.0.0 until 2.131.0, the HTML, JATS, OpenDocument spreadsheet, and BoxNote backends, including docling/backend/html_backend.py, docling/backend/jats_backend.py, and docling/backend/boxnote_backend.py, accept the rowspan and colspan attribute values without an upper bound and execute loops or allocate a table grid proportional to the declared span. A very small document can therefore cause sustained CPU use or multi-gigabyte memory allocation, and the document_timeout setting does not interrupt the single backend conversion call. Export through the TableData.grid property can further materialize the oversized grid. This issue is fixed in 2.131.0.
From the CVE record · GitHub_M
Docling’s HTML, JATS, OpenDocument spreadsheet, and BoxNote backends do not bound table rowspan and colspan values. Processing a small document with large span values can cause sustained CPU use or multi-gigabyte memory allocation; document_timeout does not interrupt the backend conversion call. The input does not specify whether network access, authentication, or user interaction is required.
Check installations of PyPI docling versions >=2.0.0 and <2.131.0 or docling-slim versions >=2.92.0 and <2.131.0.