CVE-2026-44018Medium· 5.5▾ SunlitDocling: Unsafe Archive Extraction and XML Parsing in METS-GBS Backend
▾ Sunlit zone — Low / medium · no exploitation signal
impact 30.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 13.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.1%
0.1% → 0.2%
The METS-GBS backend's XML parsing and the input document format detection lacked security controls, enabling:
An attacker could craft malicious METS-GBS archives that, when processed, could read sensitive files, exhaust system resources, or cause application crashes.
Fixed in version 2.91.0. The fix implements:
resolve_entities=False, load_dtd=False, and no_network=True_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 exceededAvoid processing METS-GBS archives from untrusted sources. If necessary, pre-validate archives in an isolated environment with resource limits.
docling >= 2.45.0, < 2.91.0Upgrade to a patched release:
docling 2.91.0Connected by shared product, vendor, weakness, or advisory.
CVE-2026-44016High· 8.2Docling: Unsafe Playwright-based HTML Rendering
CVE-2026-44017High· 7.5Docling: Unsafe Zip Extraction in EasyOCR Model Download
CVE-2026-44022Medium· 5.5Docling: Potential Path Traversal via LaTeX \includegraphics and \input Commands
CVE-2026-44020High· 7.5Docling: Unsafe XML Entity Expansion in USPTO Patent Backend
CVE-2026-31247High· 7.5Docling's JATS XML backend is vulnerable to XML Entity Expansion (XXE) attacks
CVE-2026-31248High· 7.5Docling's METS GBS backend is vulnerable to XML Entity Expansion (XXE) attacks