Categories
CVE-2026-105745 medium CVSS 6.7

Vulnerability in docling (CVE-2026-105745)

Summary

Vulnerability in docling (CVE-2026-105745). Successful exploitation can lead to full system takeover. Exploitable via docling.. Mitigation: upgrade to 2.131.0 or later.

Original description

The description as published by the source.

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 wit…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-105745 has been found in docling.
Attackers can target a specific entry point like docling. over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 6.7/10.
What to do: upgrade docling to 2.131.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-105745" on the vendor's site.

CVE-2026-105745 (docling) — CWE-696 / CVSS v3 6.7
Attack vector: local
Attack surface: docling. / allow_external_plugins / docling
Patched: 2.131.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-696) exists in docling. Attackers reach the vulnerable code path via docling..

📍 Affected scope

Check the vendor advisory for the affected versions of docling. Attack surface: docling. / allow_external_plugins / docling.

🔥 Severity

Severity: Medium (CVSS 6.7/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.131.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'docling' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'docling' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で docling を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade docling to 2.131.0

    ステージング環境で 2.131.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip docling
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.131.0"}]}]
pip docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.131.0"}]}]
PyPI docling
[{"type":"ECOSYSTEM","events":[{"introduced":"2.27.0"},{"fixed":"2.131.0"}]}]
PyPI docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"2.92.0"},{"fixed":"2.131.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details