CVE-2026-105747: Docling Memory Exhaustion Vulnerability Due to METS-GBS Archive Member Limit

docling Updated 06 Oct 2026

Summary

06/10/2026
Yes i
Moderate
4.3

CVE-2026-105747: 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(). Affects docling versions >= 2.45.0, < 2.131.0. Fixed in 2.131.0. How to fix ↓

Also tracked for

The same CVE-2026-105747 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Docling is an open-source tool designed for document conversion and management, particularly focusing on various archive formats. It allows users to convert documents into different formats while ensuring data integrity and accessibility. However, it has a vulnerability that can lead to memory exhaustion when processing gzip-compressed tar archives, specifically those formatted as METS-GBS.

Vulnerability Detail

The vulnerability arises during the format detection phase when Docling processes gzip-compressed tar archives. When the METS-GBS backend opens an archive, it calls the method tarfile.TarFile.getmembers(), which enumerates all members of the archive in memory before checking the max_member_count limit. This means that even small archives with a large number of empty members can lead to significant memory allocation, causing the application to exhaust available memory. This issue was introduced in version 2.45.0 and was exacerbated by a fix for a previous vulnerability (CVE-2026-44018) in version 2.91.0. The vulnerability can lead to memory exhaustion during the conversion process, although it does not affect the confidentiality or integrity of the data.

How To Fix

Latest published version: 2.142.0 as of 22 Oct 2026

pip install --upgrade "docling==2.142.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.131.0

This is the first release that contains the fix.

pip install --upgrade "docling==2.131.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading is not immediately possible, users can implement a workaround by rejecting gzip or tar inputs before they reach Docling when METS-GBS support is not required. Additionally, it is advisable to run conversions of untrusted input with memory limits to prevent memory exhaustion.

Conclusion

In summary, CVE-2026-105747 is a memory exhaustion vulnerability in Docling that arises during the processing of METS-GBS formatted gzip-compressed tar archives. Users are advised to upgrade to version 2.131.0 or implement workarounds to mitigate the risk of memory exhaustion.

See every vulnerability recorded for docling →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 4.3, indicating a moderate severity level.

Docling versions from 2.45.0 to 2.130.0 are affected by this vulnerability.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you cannot upgrade, consider implementing workarounds such as rejecting gzip or tar inputs when METS-GBS support is not needed and running conversions with memory limits.

No, this vulnerability does not affect the confidentiality or integrity of the data; it only poses a risk of memory exhaustion.

Related vulnerabilities

Recent vulnerabilities recorded for docling.

How To Fix

Latest published version: 2.142.0 as of 22 Oct 2026

pip install --upgrade "docling==2.142.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.131.0

This is the first release that contains the fix.

pip install --upgrade "docling==2.131.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback