CVE-2026-105749: docling · Uncontrolled Resource Consumption
Affects doclingSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.131.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.131.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade docling and docling-slim and docling-project/docling to 2.131.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| docling-projectdocling | Affected
| Fixed in
|
| docling-projectdocling-slim | Affected
| Fixed in
|
GitHubdocling-project/doclingpkg:github/docling-project/doclingOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade docling to version 2.131.0 or later where this issue is fixed. The document_timeout setting does not mitigate the vulnerability, so relying on it is insufficient. No other vendor mitigations are noted.
Description
CVE-2026-105749 is an uncontrolled resource consumption vulnerability in the docling-project's docling software. Versions from 2.0.0 up to but not including 2.131.0 allow HTML, JATS, OpenDocument spreadsheet, and BoxNote backends to accept rowspan and colspan attribute values without upper bounds. This can cause excessive CPU usage or multi-gigabyte memory allocation when processing small documents. The document_timeout setting does not interrupt the backend conversion call, exacerbating the impact. The issue is fixed in version 2.131.0.
References
- github.com/docling-project/docling/security/advisories/GHSA-cgc7-9qp3-86m3 (opens in a new tab)
- github.com/docling-project/docling/pull/4414 (opens in a new tab)
- github.com/docling-project/docling/commit/c5b4429cc6500a344c13edeb22e67610c2159b09 (opens in a new tab)
- github.com/docling-project/docling/releases/tag/v2.131.0 (opens in a new tab)