GHSA-f4ch-vxwc-3p2m: Medium severity pip/docling vulnerability

Q: Which Docling versions require remediation?

Docling versions from 2.45.0 up to, but not including, 2.131.0 are affected. The issue is fixed in version 2.131.0.

Q: Does restricting allowed document formats prevent exposure?

No. METS-GBS detection can process the archive before the allowed_formats restriction is applied, so that restriction does not prevent this issue during format detection.

Q: What input would an attacker need to provide?

An attacker would need to supply a small gzip-compressed tar archive containing a very large declared number of empty members. Processing that archive can cause memory consumption proportional to the member count.

Q: What should be used as the primary advisory record?

This advisory was withdrawn as a duplicate of GHSA-3cr3-8m4c-fpxw. Use that advisory for the maintained record while retaining this identifier for external-reference tracking.

Published Oct 6, 2026

Updated

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-3cr3-8m4c-fpxw. This link is maintained to preserve external references.

Original 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/metsgbsbackend.py call tarfile.TarFile.getmembers() before enforcing the maxmembercount 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 allowedformats 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.

Affected Software

1 affected componentFixes available

pip/docling>=2.45.0<2.131.0

2.131.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade pip/docling to a version that resolves this vulnerability.
Fixed in 2.131.0
Upgrade
Upgrade docling to a version that resolves this vulnerability.
Fixed in 2.131.0

Event History

Oct 6, 2026

Advisory Published

via GitHub·12:32 AM

Data Sourced

via GitHub·12:32 AM

DescriptionSeverityWeaknessAffected Software

Withdrawn

via GitHub·01:43 PM

Frequently Asked Questions

Which Docling versions require remediation?

Docling versions from 2.45.0 up to, but not including, 2.131.0 are affected. The issue is fixed in version 2.131.0.

Does restricting allowed document formats prevent exposure?

No. METS-GBS detection can process the archive before the allowed_formats restriction is applied, so that restriction does not prevent this issue during format detection.

What input would an attacker need to provide?

An attacker would need to supply a small gzip-compressed tar archive containing a very large declared number of empty members. Processing that archive can cause memory consumption proportional to the member count.

What should be used as the primary advisory record?

This advisory was withdrawn as a duplicate of GHSA-3cr3-8m4c-fpxw. Use that advisory for the maintained record while retaining this identifier for external-reference tracking.

GHSA-f4ch-vxwc-3p2m: Medium severity pip/docling vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which Docling versions require remediation?

Does restricting allowed document formats prevent exposure?

What input would an attacker need to provide?

What should be used as the primary advisory record?

Company

Resources

Contact

Frequently Asked Questions

Which Docling versions require remediation?

Does restricting allowed document formats prevent exposure?

What input would an attacker need to provide?

What should be used as the primary advisory record?