Docling's METS GBS backend is vulnerable to XML Entity Expansion (XXE) attacks thru 2.61.0. The backend extracts and validates XML files from .tar.gz archives using etree.fromstring() without disabling entity resolution. An attacker can craft a malicious XML file with nested entity definitions (XML Bomb) and package it into a .tar.gz archive. When processed by Docling, the exponential expansion of entities during XML parsing leads to excessive resource consumption, resulting in a denial of service (DoS) condition on the system running the Docling parser.
CVE-2026-31248
HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-11. NVD baseline CVSS 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 19.7%
- KEV
- Not listed
Published
May 11, 2026
Last Modified
May 13, 2026
Advisory Details (2)
Auto-updated Jun 6, 2026No patch confirmed yet.
generic
GitHub - docling-project/docling: Get your documents ready for gen AI · GitHub
https://github.com/docling-project/doclingVendor Advisories for CVE-2026-31248(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| pip | docling | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| docling | 0.1.0 ... 2.9.0 (137 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2026-31248?
CVE-2026-31248 is a high vulnerability published on May 11, 2026. Docling's METS GBS backend is vulnerable to XML Entity Expansion (XXE) attacks thru 2.61.0. The backend extracts and validates XML files from .tar.gz archives using etree.fromstring() without disabling entity resolution. An attacker can craft a malicious XML file with nested entity definitions (XML…
When was CVE-2026-31248 disclosed?
CVE-2026-31248 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31248 actively exploited?
CVE-2026-31248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31248?
CVE-2026-31248 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31248, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31248
Is Your Infrastructure Affected by CVE-2026-31248?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.