vulnerability / NVI-00011868 / Revision 2
Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion
GitHub lists this reviewed advisory for docling, docling-slim. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
6.5 medium
GitHub source severity; exploitability and local consequence require separate evidence.
As of · GitHub Advisory Database
0.291%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.21671. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
docling
source listed>= 2.0.0, < 2.131.0
### Summary The HTML, JATS, ODS (OpenDocument spreadsheet) and BoxNote backends accept table `rowspan` / `colspan` values without an upper bound. A few bytes of input, such as ``, make docling run loops proportional to the declared span and allocate a table grid of the declared size. The result is CPU and memory exhaustion. ### Details - `docling/backend/html_backend.py` (`_get_cell_spans`) parses span attributes with no upper limit. The cell-filling loop then iterates `row_span × col_span` times. - `docling/backend/jats_backend.py` and `docling/backend/boxnote_backend.py` fill their tables the same way. - The OpenDocument spreadsheet path scans the declared span range. - Export (for example `export_to_markdown()`) materialises the full grid through `TableData.grid` in docling-core. `document_timeout` does not bound this. It is checked between pipeline stages, and these backends convert the whole document in a single call. `max_file_size` and `max_num_pages` do not help because the payload is tiny. Measured on 2.130.0: a 54-byte HTML file with `rowspan="1e8"` takes about 4.4 s of CPU, and the time grows linearly with the value. A 52-byte file with `cols
docling-slim
source listed>= 2.92.0, < 2.131.0
### Summary The HTML, JATS, ODS (OpenDocument spreadsheet) and BoxNote backends accept table `rowspan` / `colspan` values without an upper bound. A few bytes of input, such as ``, make docling run loops proportional to the declared span and allocate a table grid of the declared size. The result is CPU and memory exhaustion. ### Details - `docling/backend/html_backend.py` (`_get_cell_spans`) parses span attributes with no upper limit. The cell-filling loop then iterates `row_span × col_span` times. - `docling/backend/jats_backend.py` and `docling/backend/boxnote_backend.py` fill their tables the same way. - The OpenDocument spreadsheet path scans the declared span range. - Export (for example `export_to_markdown()`) materialises the full grid through `TableData.grid` in docling-core. `document_timeout` does not bound this. It is checked between pipeline stages, and these backends convert the whole document in a single call. `max_file_size` and `max_num_pages` do not help because the payload is tiny. Measured on 2.130.0: a 54-byte HTML file with `rowspan="1e8"` takes about 4.4 s of CPU, and the time grows linearly with the value. A 52-byte file with `cols
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-cgc7-9qp3-86m3 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
- CVE-2026-105749 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 2 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.