Docling: Plugin entry points are imported before the allow_external_plugins check
docling-project docling · docling-project docling-slim
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| docling PyPI |
|
|
| docling-slim PyPI |
|
|
docling-project docling · docling-project docling-slim
| Product | Affected | Fixed in |
|---|---|---|
| docling PyPI |
|
|
| docling-slim PyPI |
|
|
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.
From the CVE record · GitHub_M
Docling plugin factories import all registered entry-point modules before checking whether external plugins are allowed. If a third-party or compromised plugin package is installed, its import-time code can run when Docling starts even with external plugins disabled; no network access or user interaction is described.
Check installations of PyPI docling >=2.27.0 <2.131.0 and docling-slim >=2.92.0 <2.131.0.