Skip to main content
No exploitation reportedFix available

CVE-2026-105747

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

No exploitation reported by the sources we read.

  • Published2026-10-05
  • Fixed in2.131.0
  • WeaknessCWE-409 · CWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-10-0522:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-105747?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-105747?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Docling
BranchAffectedFixed in
2.x≥ 2.45.0, < 2.131.02.131.0
2.x≥ 2.92.0, < 2.131.02.131.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-105747 Red Hat Product Security7 known affected

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

    lightspeed-core/rag-tool-cpu-rhel9 as a component of Lightspeed Core · lightspeed-core/rag-tool-cuda-12.9-rhel9 as a component of Lightspeed Core · rhai-early-access/docling-sdk-cuda-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · +4 more

Full record on NVD

Fix

  1. Update Docling to 2.131.0
  2. Workaround from the vendor Red Hat Product Security CVE-2026-105747 · 7 productsA 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…
  3. No fix available, says the vendor Red Hat Product Security CVE-2026-105747 · 7 productsFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-10-06
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.14.3read 2026-10-23
  • CNAweakness (CWE)CWE-409, CWE-770read 2026-10-23
  • FIRST EPSSEPSS score0.2 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Published
2026-10-05
Last Modified
2026-10-07
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-105747?

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.

Is CVE-2026-105747 actively exploited?

Active exploitation of CVE-2026-105747 has not been confirmed. Its EPSS score was 0.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-105747?

CVE-2026-105747 has a CVSS v3 base score of 4.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L.

Running docling? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database