CVE-2026-105745 docling-project CVE debrief

Who should care

Defenders responsible for maintaining and securing environments where the docling package is used should be aware of this vulnerability. This includes teams managing Python environments, especially those using unvetted or compromised dependencies.

Why it matters

CVE-2026-105745 is a vulnerability in the docling package that allows import-time code in installed third-party plugins to run even when external plugins are disabled. Defenders should prioritize verifying the docling package version, reviewing installed dependencies, and configuring the allow_external_plugins setting to prevent external plugin imports.

• Execution of third-party plugin modules may occur even when external plugins are disabled
• Import-time code in installed third-party plugins may run unexpectedly
• Verification of docling package version and allow_external_plugins setting configuration is necessary
• Review of installed dependencies for unvetted or compromised packages is required

Technical summary

The docling package imports plugin entry points before applying the allow_external_plugins check. This allows import-time code in installed third-party plugins to run even when external plugins are disabled. As a result, defenders should prioritize verifying the docling package version and ensuring that the allow_external_plugins setting is properly configured. They should also review installed dependencies for any unvetted or compromised packages that may be registering docling plugin entry points. This oversight in the plugin loading process can lead to unexpected execution of third-party plugin modules, potentially resulting in security risks. To mitigate these risks, it is crucial to maintain up-to-date doc

Defensive priority

Defenders should prioritize verifying the docling package version and ensuring that the allow_external_plugins setting is properly configured. They should also review installed dependencies for any unvetted or compromised packages that may be registering docling plugin entry points.

Recommended defensive actions

• Verify the docling package version and ensure it is up-to-date
• Review installed dependencies for any unvetted or compromised packages
• Configure the allow_external_plugins setting to prevent external plugin imports
• Monitor for any suspicious activity related to docling plugin imports
• Perform a thorough review of the environment for any signs of exploitation
• Consider implementing additional security measures to prevent similar vulnerabilities
• Track and document the verification process and findings

Evidence notes

The vulnerability is caused by docling's plugin factories calling pluggy's load_setuptools_entrypoints() function, which imports all modules registered under the docling plugin entry-point group. The allow_external_plugins check is applied only after these modules have been imported. This means that import-time code in any installed third-party plugin will run, even if external plugins are disabled.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.