CVE-2026-105747

Received Received - Intake

Memory Exhaustion in Docling via Malformed Tar Archive

Publication date: 2026-10-05

Last updated on: 2026-10-05

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-05

Last Modified

2026-10-05

Generated

2026-10-06

AI Q&A

2026-10-06

EPSS Evaluated

N/A

NVD

CVE-2026-105747

EUVD

EUVD-2026-92809

Affected Vendors & Products

Vendor	Product	Version / Range
docling-project	docling	>= 2.45.0, < 2.131.0
docling-project	docling-slim	>= 2.45.0, < 2.131.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-409	The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.
CWE-770	The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

Executive Summary

This vulnerability affects Docling, a document processing tool. Between versions 2.45.0 and 2.131.0, the software incorrectly handles tar archives by loading the full member list into memory before checking size limits. This allows a specially crafted tar file with many empty members to consume excessive memory during format detection.

Detection Guidance

This vulnerability involves memory exhaustion due to improper handling of tar archives with excessive members in Docling versions 2.45.0 to 2.131.0. To detect it, monitor system memory usage during document processing tasks and inspect logs for tar archive parsing errors. Check Docling version with 'pip show docling' or 'docling --version'.

Impact Analysis

An attacker could exploit this to cause a denial of service by crashing the application or consuming system resources. Users running affected versions may experience slowdowns or crashes when processing malicious tar files.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR or HIPAA by enabling denial-of-service (DoS) attacks through memory exhaustion. A malicious actor could craft a small tar archive with many empty members, causing excessive memory consumption during format detection. This may lead to system instability or crashes, which could disrupt services handling sensitive data, violating availability requirements in GDPR or HIPAA.

Mitigation Strategies

Upgrade Docling to version 2.131.0 or later immediately. If upgrading is not possible, restrict processing of tar archives or implement memory limits during document parsing. Disable METS-GBS format detection if not required.

Hi! I’m here to help you understand CVE-2026-105747. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70