What is the CVSS score of EUVD-2026-29095?

EUVD-2026-29095 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.0%.

Which versions of Docling are affected by EUVD-2026-29095?

Docling METS GBS backend versions 2.61.0 and earlier are vulnerable to remote denial-of-service attacks through malicious .tar.gz archives containing XML bombs that trigger exponential entity…

How to fix or mitigate EUVD-2026-29095?

Within 24 hours, conduct an inventory of systems running Docling METS GBS backend version 2.61.0 or earlier, particularly those processing external or untrusted .tar.gz files, and assess exposure by reviewing document processing workflows. Within 7 days, implement interim controls including disabling XML entity expansion if configurable in the backend, enforcing strict input validation and size limits on uploaded archives, deploying network-level filtering to block suspicious .tar.gz uploads, and implementing CPU and memory resource quotas on affected backend processes. Within 30 days, actively monitor vendor advisories for patch availability, evaluate alternative document processing solutions, or consider containerizing the backend with strict resource constraints as a long-term compensating control.

Docling EUVD-2026-29095

| CVE-2026-31248 HIGH

Improper Restriction of Recursive Entity References in DTDs (CWE-776)

2026-05-11 mitre

GHSA-9f4q-q82q-4359

Denial Of Service XXE N A

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

vuln.today AI

7.5 HIGH

Untrusted archive parsed without entity hardening enables unauthenticated remote DoS (A:H); no confidentiality or integrity impact, matching CWE-776 entity-expansion behavior.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 24, 2026 - 00:01 vuln.today

CVSS changed

May 12, 2026 - 19:22 NVD

7.5 (HIGH)

CVE Published

May 11, 2026 - 00:00 nvd

HIGH 7.5

CVE Published

May 11, 2026 - 00:00 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

Denial of service in Docling's METS GBS backend (through version 2.61.0) allows remote attackers to exhaust CPU and memory by submitting a malicious .tar.gz archive containing an XML bomb. The backend parses embedded XML with etree.fromstring() while entity resolution remains enabled, so recursively nested entity definitions expand exponentially during parsing and stall or crash the host processing the document. EPSS is very low (0.02%) and there is no public exploit code or KEV listing, but a vendor-published Notion write-up describes the flaw in detail.

Technical ContextAI

Docling is an open-source document-conversion and parsing library widely used in AI/RAG document-ingestion pipelines. The affected component is the METS GBS backend, which handles Google Books-style METS packages delivered as gzip-compressed tar archives and extracts/validates the contained XML using Python's lxml etree.fromstring(). Because the parser is invoked without a hardened configuration (no resolve_entities=False / no_network / DTD-loading disabled), internal entity references are expanded at parse time. This maps to CWE-776 (Improper Restriction of Recursive Entity References in DTDs, i.e. 'XML Entity Expansion' / Billion Laughs). Note that although the report is tagged XXE, the described impact is entity-expansion resource exhaustion rather than external-entity file disclosure or SSRF; no confidentiality or integrity impact is claimed, consistent with the C:N/I:N/A:H CVSS vector.

RemediationAI

Upgrade Docling to a release later than 2.61.0 that hardens the METS GBS XML parsing; no exact fixed version is present in the provided data, so treat patch status as 'fix pending independent confirmation' and verify the fixed tag against the project repository (https://github.com/docling-project/docling) and the vendor write-up (https://www.notion.so/CVE-2026-31248-35d1e1393188818585b2ce3b9ce24686) before deploying. As compensating controls until patched: avoid or disable the METS GBS backend if your pipeline does not need it; validate and reject untrusted .tar.gz/METS uploads before parsing; enforce archive-size and decompression limits and run parsing in a CPU/memory-capped sandbox or container with strict resource ceilings and timeouts so an XML bomb crashes only the worker, not the host; and where you control the parsing call, configure lxml to disable entity resolution and DTD loading (e.g. an XMLParser with resolve_entities=False, no_network=True, load_dtd=False). The trade-offs: disabling the backend removes METS support, size/time limits may reject legitimate large documents, and sandboxing adds operational overhead.