CVE-2026-105745

Received Received - Intake

Remote Code Execution in Docling Document Processing Library

Publication date: 2026-10-05

Last updated on: 2026-10-05

Assigner: GitHub, Inc.

Description

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.27.0 until 2.131.0, Docling plugin factories in docling/models/factories/base_factory.py call load_setuptools_entrypoints() before applying the allow_external_plugins setting, so every module registered in the Docling entry-point group is imported even when external plugins are disabled. An installed third-party or compromised package can therefore execute import-time code when Docling starts, while the subsequent namespace filter misleadingly reports that the plugin was not loaded. This issue is fixed in 2.131.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-05

Last Modified

2026-10-05

Generated

2026-10-06

AI Q&A

2026-10-06

EPSS Evaluated

N/A

NVD

CVE-2026-105745

Affected Vendors & Products

Vendor	Product	Version / Range
docling-project	docling	>= 2.27.0, < 2.131.0
docling-project	docling-slim	>= 2.27.0, < 2.131.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-696	The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
CWE-829	The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

Attack-Flow Graph

Executive Summary

Docling versions 2.27.0 to 2.131.0 have a flaw where plugin factories import all registered modules before checking the allow_external_plugins setting. This allows malicious or compromised packages to execute code during Docling startup, even when external plugins are supposedly disabled.

Detection Guidance

Check Docling version with pip show docling. If version is between 2.27.0 and 2.130.0, the system is vulnerable. Review installed plugins and third-party packages for suspicious imports.

Impact Analysis

An attacker could exploit this to run arbitrary code on your system when Docling starts, potentially stealing data, installing malware, or disrupting operations. The vulnerability bypasses intended security controls by misleadingly reporting that external plugins were not loaded.

Compliance Impact

This vulnerability could lead to unauthorized code execution, potentially causing data breaches or unauthorized access to sensitive information. This may violate compliance requirements for data protection and security controls in standards like GDPR and HIPAA.

Mitigation Strategies

Upgrade Docling to version 2.131.0 or later. Disable external plugins if not needed. Audit installed packages for untrusted imports.

Hi! I’m here to help you understand CVE-2026-105745. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70