Skip to main content
VulnerabilityPublished

CVE-2026-105747: docling · Data Amplification

Affects doclingSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.131.0 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 23% 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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Upgrade docling and docling-slim and docling-project/docling to 2.131.0.

Affected software

ProductAffectedFixed in
docling-projectdoclingAffected
  • >=2.45.0 <2.131.0
Fixed in
  • 2.131.0
docling-projectdocling-slimAffected
  • >=2.45.0 <2.131.0
Fixed in
  • 2.131.0
GitHubdocling-project/doclingpkg:github/docling-project/doclingOther threatsAffected
  • >=2.45.0 <2.131.0
Fixed in
  • 2.131.0

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. No other mitigations are specified or required.

Description

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.45.0 until 2.131.0, METS-GBS format detection in docling/datamodel/document.py and the backend in docling/backend/mets_gbs_backend.py call tarfile.TarFile.getmembers() before enforcing the max_member_count limit, causing the full archive member list to be allocated before the limit can stop processing. A small gzip-compressed tar archive with a very large number of empty members can therefore consume memory proportional to the declared member count, including during format detection before the allowed_formats restriction is applied. This issue is a residual weakness in the member-count protection added for CVE-2026-44018. This issue is fixed in 2.131.0.

References

Community reviews

Loading reviews…