Skip to content
Fencer Vulns
medium 4.3

CVE-2026-105747 json

Docling: METS-GBS archive member limit enforced after full member enumeration (memory exhaustion during format detection)

published 2026-10-05 34 d ago modified 2026-10-15 24 d ago also GHSA-3cr3-8m4c-fpxw , PYSEC-2026-4194 , PYSEC-2026-4209 , EUVD-2026-92809

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi docling 2.131.0
  • pypi docling-slim 2.131.0
  • docling docling 2.131.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-105747 updated cvss 4.3

docling: docling: Denial of Service via excessive memory allocation in archive processing

  • Red Hat Lightspeed Core lightspeed-core/rag-tool-cpu-rhel9, lightspeed-core/rag-tool-cuda-12.9-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-autorag-rhel9, rhoai/odh-ogx-core-rhel9, rhoai/odh-feature-server-rhel9, rhai-early-access/docling-sdk-cuda-rhel9, rhai-early-access/docling-serve-cuda-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
33 d ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
OSV 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
pypi docling
>=2.45.0, <2.131.0
2.131.0
pypi docling-slim
>=2.92.0, <2.131.0
2.131.0

Affected products

  • docling-project docling
  • docling-project docling-slim

Classification

Weakness
  • CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.