By vendor

Docling vulnerabilities

Known CVEs affecting Docling products, prioritized by severity, with SEC.co remediation and detection guidance.

6 published vulnerabilities

• CVE-2026-44016HIGH 8.2

  Docling is a document processing library that handles multiple file formats and integrates with AI systems. Versions 2.82.0 through 2.90.x contain a flaw in the HTML rendering feature (an optional capability that must be explicitly enabled). When processing untrusted HTML documents, the Playwright-based renderer can execute arbitrary JavaScript code and make unrestricted network requests, potentially exposing internal services or exfiltrating sensitive data. The vulnerability requires user interaction—specifically, processing a malicious HTML file—but once triggered, can lead to complete compromise of the rendering environment. The fix is available in version 2.91.0.

• CVE-2026-44017HIGH 7.5

  Docling, a document processing library, contains a vulnerability in how it downloads and extracts AI model files. Before version 2.91.0, the software did not properly validate file paths when extracting ZIP archives, allowing an attacker who intercepts or compromises the model download source to write files anywhere on the system where the application has write access. This could lead to remote code execution, persistent backdoors, or data destruction. The vulnerability requires attackers to first compromise the download source—either through supply chain attacks, DNS spoofing, or man-in-the-middle interception—making it a moderately difficult but high-impact attack.

• CVE-2026-44020HIGH 7.5

  Docling, a document processing library that handles multiple file formats and integrates with AI systems, contains a critical XML parsing vulnerability in its USPTO patent document handlers. Versions 2.13.0 through 2.74.0 parse untrusted XML without protection against external entity injection. An attacker who can supply a malicious USPTO patent XML file to an affected Docling deployment can read sensitive files from the server, pivot to internal systems via SSRF, or exhaust resources to crash the service. The vulnerability was resolved in version 2.74.0.

• CVE-2026-47214HIGH 7.1

  Docling, a document processing library that converts various file formats and integrates with AI systems, contains a vulnerability in its HTML parser that mishandles URIs and file paths. An attacker can exploit this by crafting a malicious document that, when processed by a user, could leak sensitive information or cause the application to become unavailable. The vulnerability affects versions prior to 2.94.0 and requires user interaction to trigger.

• CVE-2026-44018MEDIUM 5.5

  Docling, a document processing library that integrates with AI systems, contains a vulnerability in how it handles METS-GBS (a specialized XML-based document archive format) files. Versions 2.45.0 through 2.90.x lack proper security checks when parsing these archives. An attacker could create a malicious METS-GBS file that, when opened by a user in an application using vulnerable Docling, could read files from the system, consume excessive memory or CPU, or crash the application. The vulnerability requires user interaction—the file must be opened—but doesn't require special privileges to trigger.

• CVE-2026-44022MEDIUM 5.5

  Docling, a document processing library, contains a path traversal vulnerability in how it handles LaTeX file inclusion commands. An attacker can craft a malicious LaTeX document that, when processed by Docling, reads arbitrary files from the system and includes them in the converted output. This affects versions 2.73.0 through 2.90.x. The vulnerability requires user interaction—someone must process the attacker-supplied LaTeX document—but once triggered, the attacker gains read access to any file the Docling process can access, potentially exposing credentials, configuration data, or other sensitive information.