cve.bz

CVE-2026-105747 docling docling

4.3 mediumEPSS 0.3%Fix available

Medium (4.3) 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.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.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. 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-409 Improper Handling of Highly Compressed Data (Data Amplification)
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105747 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105747?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105747?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-105747 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.45.0 before 2.131.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3cr3-8m4c-fpxwPyPIdocling>=2.45.0 <2.131.02.131.0
GHSA-3cr3-8m4c-fpxwPyPIdocling-slim>=2.92.0 <2.131.02.131.0
PYSEC-2026-4194PyPIdocling>=2.45.0 <2.131.02.131.0
PYSEC-2026-4209PyPIdocling-slim>=2.92.0 <2.131.02.131.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A MODERATE severity denial of service vulnerability was found in docling, a document conversion library shipped in Red Hat OpenShift AI (RHOAI) and Lightspeed Core products. When docling performs METS-GBS format detection on a gzip-compressed tar archive, and when the METS-GBS backend later opens it, the full archive member list is enumerated in memory before the configured member-count limit is enforced. A remote attacker who can submit or trigger processing of a specially crafted compressed archive containing an extremely large number of entries (for example, empty members) can therefore cause memory allocation proportional to the declared member count, potentially exhausting system memory and crashing the application or rendering it unresponsive. Only availability is affected; confidentiality and integrity are not. This issue is a residual weakness in the member-count protection previously added for CVE-2026-44018. The Red Hat severity of MODERATE (CVSS 4.3) is consistent with the upstream assessment. For the affected Red Hat OpenShift AI and Lightspeed Core components, the fix has been deferred because the impact is moderate with a CVSS score below the level that warrants filing update trackers for these offerings; the residual risk is a temporary denial of service of the document conversion process, which can be reduced by controlling which documents are accepted for processing. The rhoai-3.3 stream is out of support scope.

Red Hat's mitigation

A fix is available upstream in docling 2.131.0, which reads archive members incrementally and stops as soon as the member-count limit is exceeded. For deployments that cannot yet upgrade, the upstream project recommends rejecting gzip or tar inputs before they reach docling when METS-GBS support is not needed, and running conversions of untrusted input with memory limits so that excessive memory allocation cannot exhaust the host.

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-105747.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON