Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion

CVE-2026-105749GHSA-cgc7-9qp3-86m3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (docling-slim 2.131.0; docling 2.131.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI docling-slim

    Affected
    >= 2.92.0, < 2.131.0
    Fixed in
    2.131.0

  • PyPI docling

    Affected
    >= 2.0.0, < 2.131.0
    Fixed in
    2.131.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-105749: 0.29% estimated exploitation activity in the next 30 days; percentile 21.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 <td rowspan="100000000", 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/htmlbackend.py (getcellspans) parses span attributes with no upper limit. The cell-filling loop then iterates rowspan × colspan times. - docling/backend/jatsbackend.py and docling/backend/boxnotebackend.py fill their tables the same way. - The OpenDocument spreadsheet path scans the declared span range. - Export (for example exporttomarkdown()) materialises the full grid through TableData.grid in docling-core. documenttimeout does not bound this. It is checked between pipeline stages, and these backends convert the whole document in a single call. maxfilesize and maxnumpages do not help because the payload is tiny. Measured…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-cgc7-9qp3-86m3

  2. Revision 2 · amended ·

    Amended from osv record GHSA-cgc7-9qp3-86m3

  3. Revision 1 · created ·

    Published from ghsa record GHSA-cgc7-9qp3-86m3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-105749

Advisory: Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion
IDs: CVE-2026-105749, GHSA-cgc7-9qp3-86m3
Record: https://patchnext.com/advisories/cve-2026-105749 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: docling-slim 2.131.0; docling 2.131.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI docling-slim: affected >= 2.92.0, < 2.131.0; fixed in 2.131.0
- PyPI docling: affected >= 2.0.0, < 2.131.0; fixed in 2.131.0

## Suggested inspection (read-only)
- `python -m pip show docling-slim`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show docling`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on docling-slim, docling.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cgc7-9qp3-86m3 (GitHub-reviewed advisory GHSA-cgc7-9qp3-86m3 lists affected ranges: PyPI docling >=2.0.0 =2.92.0 <2.131.0)
- Verified: https://osv.dev/vulnerability/GHSA-cgc7-9qp3-86m3 (OSV record GHSA-cgc7-9qp3-86m3 lists affected ranges: PyPI docling >=2.0.0 =2.92.0 <2.131.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…