CVE-2026-105745: Docling imports plugin entry points before the allow_external_plugins check
Summary allowexternalplugins=False (the default, and the CLI default) is meant to restrict docling to its own model plugins. However, docling's plugin factories call pluggy's loadsetuptoolsentrypoints(), which imports every module registered under docling's plugin entry-point group. Only afterwards does docling filter out modules outside the docling. namespace.
Published Oct 7, 2026
Affected packages
docling
- Ecosystem
- PyPI
- Affected
- >= 2.27.0, < 2.131.0
- Fixed in
- 2.131.0
- Check
pip show docling
docling-slim
- Ecosystem
- PyPI
- Affected
- >= 2.92.0, < 2.131.0
- Fixed in
- 2.131.0
- Check
pip show docling-slim
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
allow_external_plugins=False (the default, and the CLI default) is meant to restrict docling to its own model plugins. However, docling's plugin factories call pluggy's load_setuptools_entrypoints(), which imports every module registered under docling's plugin entry-point group. Only afterwards does docling filter out modules outside the docling. namespace. Import-time code in any installed third-party plugin therefore runs even though external plugins are disabled.
Details
In docling/models/factories/base_factory.py, load_from_plugins() loads all entry points first and applies the allow_external_plugins check only to the already-imported modules. The CLI creates these factories when it starts, so running docling imports every registered plugin module. A log message says the plugin "will not be loaded", although its module has already been imported.
Affected configurations
Environments in which a package registering a docling plugin entry point is installed, for example an unvetted or compromised dependency, and which rely on allow_external_plugins=False to keep that code from running.
Impact
Execution of a third-party plugin module's import-time code in the docling process, contrary to the documented behaviour of allow_external_plugins=False.
Patches
Fixed in docling 2.131.0 by #4413. Plugin entry points are now filtered by module name before they are loaded, so with allow_external_plugins=False third-party plugin modules are no longer imported.
Workarounds
Upgrade to 2.131.0. For older versions:
Only install trusted packages in environments that run docling. Check which packages register docling plugin entry points with importlib.metadata.entry_points().
Credited to hypnguyen1209.
References
- https://github.com/docling-project/docling/security/advisories/GHSA-9jxx-vjrv-h2rq
- https://nvd.nist.gov/vuln/detail/CVE-2026-105745
- https://github.com/docling-project/docling/pull/4413
- https://github.com/docling-project/docling/commit/0f443b3786e98688a2da3b7c8f56fe5e46af876c
- https://github.com/docling-project/docling/releases/tag/v2.131.0
- https://github.com/advisories/GHSA-9jxx-vjrv-h2rq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-105742
Docling: Configured HTTP headers sent to every remote image host named by a document
low3.7Oct 7, 2026CVE-2026-105743
Docling has SSRF guard bypass in remote resource fetching (DNS rebinding / multi-record resolution; no IP validation in HTML render mode)
medium4.0Oct 7, 2026CVE-2026-105744
Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine
high7.5Oct 7, 2026CVE-2026-105748
Docling: Crafted DoclingDocument JSON embeds local image files into converted output
medium4.3Oct 7, 2026CVE-2026-105749
Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion
medium6.5Oct 7, 2026CVE-2026-105747
Docling: METS-GBS archive member limit enforced after full member enumeration (memory exhaustion during format detection)
medium4.3Oct 6, 2026
