INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-44018

Docling: Unsafe Archive Extraction and XML Parsing in METS-GBS Backend

CVE-2026-44018 ยท 2026-06-03 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Information exposure
Affected
docling (PyPI)
CVSS
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

The METS-GBS backend parsed XML with external entities enabled and extracted archives without limits, allowing local file reads and resource exhaustion from crafted input. (Our summary, written by a model. The source text is below.)

Details

Impact

The METS-GBS backend's XML parsing and the input document format detection lacked security controls, enabling: - XML External Entity (XXE) attacks to read local files or cause denial of service - Decompression bombs (zip bombs) to exhaust memory and disk space - Unbounded archive extraction consuming system resources

An attacker could craft malicious METS-GBS archives that, when processed, could read sensitive files, exhaust system resources, or cause application crashes.

Patches

Fixed in version 2.91.0. The fix implements: - Secure XML parsing with resolve_entities=False, load_dtd=False, and no_network=True - Configurable limits: 300 MB total extraction size, 10 MB per file, 1000 member count - Cumulative size tracking across all extractions - Early termination when limits are exceeded - Secure format detection of METS-GBS tar archives with _detect_mets_gbs() method: maximum file size (10 MB per file), maximum member count (1000 members), and exception handling to gracefully fail when limits are exceeded

Workarounds

Avoid processing METS-GBS archives from untrusted sources. If necessary, pre-validate archives in an isolated environment with resource limits.

References

- Fix release: v2.91.0

References

Source: GitHub Advisory Database, used under CC BY 4.0.