Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.45.0 until 2.91.0, the METS-GBS backend's XML parsing and the input document format detection lacked security controls. An attacker could craft malicious METS-GBS archives that, when processed, could read sensitive files, exhaust system resources, or cause application crashes. This vulnerability is fixed in 2.91.0.
CVE-2026-44018
This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EPSS
- 1.7%
- KEV
- Not listed
Published
June 3, 2026
Last Modified
June 27, 2026
Advisory Details (2)
Auto-updated Jun 26, 2026Unsafe Archive Extraction and XML Parsing in METS-GBS Backend · Advisory · docling-project/docling · GitHub
Affected: version 2.91.0. The fix implements:
https://github.com/docling-project/docling/security/advisories/GHSA-r3xg-rg9j-67fvRelease v2.91.0 (docling-project/docling)
Patch available: docling-project/docling v2.91.0
https://github.com/docling-project/docling/releases/tag/v2.91.0Vendor Advisories for CVE-2026-44018(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| docling | 2.45.0 ... 2.90.0 (55 versions) | 2.91.0 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 23:12 UTCEG score recompute▲ 1.60
- 2026-06-27 21:42 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
- 2026-06-14 23:18 UTCEPSS rescore
Show 3 moreShow fewer
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-03 22:10 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-44018?
When was CVE-2026-44018 disclosed?
Is CVE-2026-44018 actively exploited?
What is the CVSS score of CVE-2026-44018?
How do I remediate CVE-2026-44018?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44018
Is Your Infrastructure Affected by CVE-2026-44018?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.