cve.bz

CVE-2026-105749 docling docling: Uncontrolled Resource Consumption

6.5 mediumExploit referenceEPSS 0.3%Fix available

Medium (6.5) in docling docling. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in docling 2.131.0.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105749 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105749?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105749?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105749 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
docling:doclingfrom 2.0.0 before 2.131.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cgc7-9qp3-86m3PyPIdocling>=2.0.0 <2.131.02.131.0
GHSA-cgc7-9qp3-86m3PyPIdocling-slim>=2.92.0 <2.131.02.131.0
PYSEC-2026-4195PyPIdocling>=2.0.0 <2.131.02.131.0
PYSEC-2026-4211PyPIdocling-slim>=2.92.0 <2.131.02.131.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat rates this docling flaw as having MODERATE security impact (CVSS 3.1 score 6.5, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), consistent with the upstream assessment. A denial of service flaw was found in the docling document conversion library, which Red Hat ships bundled in Red Hat OpenShift AI (RHOAI) and Lightspeed Core container images. The HTML, JATS, OpenDocument spreadsheet, and BoxNote backends accept rowspan and colspan attribute values without an upper bound and run loops or allocate a table grid proportional to the declared span. As a result, a remote attacker who supplies a very small, specially crafted document can cause sustained CPU use or multi-gigabyte memory allocation, exhausting system resources and leaving the application unresponsive. The document_timeout setting does not interrupt the affected backend conversion call, and exporting the oversized table through the TableData.grid property can further materialize it. Exploitation requires that a user or automated pipeline accept and parse the malicious document, and the impact is limited to the availability of the conversion process. All currently mapped RHOAI and Lightspeed Core streams that bundle docling are affected. For the in-support streams the fix is deferred because this flaw is rated MODERATE with a CVSS score below 7.0, so remediation is not currently scheduled and the residual risk is a remote denial of service against services that process untrusted documents. The RHOAI 3.3 stream is likewise affected but is out of support scope.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. In particular, the docling document_timeout setting does not interrupt the vulnerable backend conversion call and therefore does not prevent the resource exhaustion. The upstream docling project has fixed this issue in version 2.131.0.

ProductPackageStateAdvisory
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Fix deferred
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-sdk-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-serve-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-autorag-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105749.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON