CVE-2026-105747: Docling: METS-GBS archive member limit enforced after full member enumeration (memory exhaustion during format detection)
Summary When docling detects the input format of a gzip-compressed tar archive (METS-GBS), and later when the METS-GBS backend opens it, it calls tarfile.TarFile.getmembers(). That builds the full member list in memory before the maxmembercount limit is checked.
Published Oct 6, 2026
Affected packages
docling
- Ecosystem
- PyPI
- Affected
- >= 2.45.0, < 2.131.0
- Fixed in
- 2.131.0
- Check
pip show docling
docling-slim
- Ecosystem
- PyPI
- Affected
- >= 2.92.0, < 2.131.0
- Fixed in
- 2.131.0
- Check
pip show docling-slim
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When docling detects the input format of a gzip-compressed tar archive (METS-GBS), and later when the METS-GBS backend opens it, it calls tarfile.TarFile.getmembers(). That builds the full member list in memory before the max_member_count limit is checked. A small archive with a very large number of empty members therefore makes docling allocate memory in proportion to the member count, and the limit has no effect.
Details
docling/datamodel/document.py (format detection) and docling/backend/mets_gbs_backend.py both iterate tar.getmembers() and count members inside the loop. getmembers() reads every header up front.
Measured on Python 3.12: an archive of 1,000,000 empty members compresses to about 6.2 MB and makes getmembers() hold about 408 MB (about 66 times the input size). Format detection runs for any application/gzip input before allowed_formats is applied, so the allocation happens even when METS-GBS is not an allowed format.
This check was introduced by the fix for CVE-2026-44018 (GHSA-r3xg-rg9j-67fv) in 2.91.0. The eager enumeration it relies on has been there since METS-GBS detection was added in 2.45.0.
Impact
Memory exhaustion of the converting process, proportional to the size of the input archive. Confidentiality and integrity are not affected.
Patches
Fixed in docling 2.131.0 by #4412. Format detection and the METS-GBS backend now read archive members one at a time and stop as soon as max_member_count is exceeded, including when looking up page files.
Workarounds
Upgrade to 2.131.0. For older versions:
Reject gzip or tar inputs before they reach docling when METS-GBS support is not needed, and run conversions of untrusted input with memory limits.
Credited to jonathanlotan, wittjeff.
References
- https://github.com/docling-project/docling/security/advisories/GHSA-3cr3-8m4c-fpxw
- https://nvd.nist.gov/vuln/detail/CVE-2026-105747
- https://github.com/docling-project/docling/pull/4412
- https://github.com/docling-project/docling/commit/ebae65cd71c37c88b36185b406a449b92d8f7ffa
- https://github.com/docling-project/docling/releases/tag/v2.131.0
- https://github.com/advisories/GHSA-3cr3-8m4c-fpxw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-105742
Docling: Configured HTTP headers sent to every remote image host named by a document
low3.7Oct 7, 2026CVE-2026-105743
Docling has SSRF guard bypass in remote resource fetching (DNS rebinding / multi-record resolution; no IP validation in HTML render mode)
medium4.0Oct 7, 2026CVE-2026-105744
Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine
high7.5Oct 7, 2026CVE-2026-105745
Docling imports plugin entry points before the allow_external_plugins check
medium6.7Oct 7, 2026CVE-2026-105748
Docling: Crafted DoclingDocument JSON embeds local image files into converted output
medium4.3Oct 7, 2026CVE-2026-105749
Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion
medium6.5Oct 7, 2026
