Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 05 Oct 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Docling-project
Docling-project docling |
|
| Vendors & Products |
Docling-project
Docling-project docling |
Mon, 05 Oct 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Docling: Plugin entry points are imported before the allow_external_plugins check | |
| Weaknesses | CWE-696 CWE-829 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-05T21:29:23.561Z
Reserved: 2026-10-05T19:11:07.946Z
Link: CVE-2026-105745
No data.
Status : Received
Published: 2026-10-05T22:16:57.330
Modified: 2026-10-05T22:16:57.330
Link: CVE-2026-105745
No data.
OpenCVE Enrichment
Updated: 2026-10-05T22:30:19Z