Skip to content
Fencer Vulns
medium 6.7

CVE-2026-105745 json

Docling: Plugin entry points are imported before the allow_external_plugins check

published 2026-10-05 34 d ago modified 2026-10-15 24 d ago also GHSA-9jxx-vjrv-h2rq , PYSEC-2026-4192 , PYSEC-2026-4210 , EUVD-2026-92805

cvss
6.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi docling 2.131.0
  • pypi docling-slim 2.131.0
  • docling docling 2.131.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-105745 updated cvss 6.7

docling: docling: Arbitrary code execution via premature plugin loading

  • Red Hat Lightspeed Core lightspeed-core/rag-tool-cpu-rhel9, lightspeed-core/rag-tool-cuda-12.9-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-autorag-rhel9, rhoai/odh-ogx-core-rhel9, rhoai/odh-feature-server-rhel9, rhai-early-access/docling-sdk-cuda-rhel9, rhai-early-access/docling-serve-cuda-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
33 d ago

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OSV 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
GitHub 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
OSV 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi docling
>=2.27.0, <2.131.0
2.131.0
pypi docling-slim
>=2.92.0, <2.131.0
2.131.0

Affected products

  • docling-project docling
  • docling-project docling-slim

Classification

Weakness
  • CWE-696 Incorrect Behavior Order
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.