Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.11% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-105745High confidence
Docling: Plugin entry points are imported before the allow_external_plugins check
docling-project · docling
Official source article: GitHub GHSA-9JXX-VJRV-H2RQ ↗. Check the applicable product and release in the original source.
6.7MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 6 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs docling-project docling and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 7 affected or under-investigation product states without a fixed product state in the same current advisory
Open-source package ranges4 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| PyPIdocling | ECOSYSTEM: introduced 2.27.0; fixed 2.131.0 | 2.131.0 | OSV record ↗aggregator derived · 7 Oct 2026 |
| PyPIdocling-slim | ECOSYSTEM: introduced 2.92.0; fixed 2.131.0 | 2.131.0 | OSV record ↗aggregator derived · 7 Oct 2026 |
| pipdocling | >= 2.27.0, < 2.131.0 | 2.131.0 | GitHub advisory ↗upstream repository advisory · 7 Oct 2026 |
| pipdocling-slim | >= 2.92.0, < 2.131.0 | 2.131.0 | GitHub advisory ↗upstream repository advisory · 7 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-105745 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitydocling: docling: Arbitrary code execution via premature plugin loading
The vendor explicitly identifies these products as affected by this CVE.
- lightspeed-core/rag-tool-cpu-rhel9 as a component of Lightspeed Core
- lightspeed-core/rag-tool-cuda-12.9-rhel9 as a component of Lightspeed Core
- rhai-early-access/docling-sdk-cuda-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhai-early-access/docling-serve-cuda-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-autorag-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ogx-core-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- Summary
- A flaw was found in Docling. Docling imports registered plugin entry points before evaluating whether external plugins are permitted. A local attacker or compromised package installed in the environment can exploit this flaw to achieve arbitrary code execution during startup, even when external plugins are explicitly disabled.
- Remediation
- Fix deferred
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Incorrect Behavior Order → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- Required interaction required
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-696 ↗
CWE-696: Incorrect Behavior Order. The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- lightspeed-core/rag-tool-cpu-rhel9 as a component of Lightspeed Core
- lightspeed-core/rag-tool-cuda-12.9-rhel9 as a component of Lightspeed Core
- rhai-early-access/docling-sdk-cuda-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhai-early-access/docling-serve-cuda-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-autorag-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-ogx-core-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 5 Oct 2026 · Last source change 6 Oct 2026, 14:48 UTC · CWE-696 · Incorrect Behavior Order
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-10-06
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-92805
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/0f443b3786e98688a2da3b7c8f56fe5e46af876c; added patch: github.com/4413; 2 further additions.security-advisories@github.com ↗
- Before
- no authoritative guidance recorded
- After
- patch: github.com/0f443b3786e98688a2da3b7c8f56fe5e46af876c · patch: github.com/4413 · patch: github.com/GHSA-9jxx-vjrv-h2rq · 1 more references
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- docling: >= 2.27.0, < 2.131.0; docling-slim: >= 2.27.0, < 2.131.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- docling: >= 2.27.0, < 2.131.0; docling-slim: >= 2.27.0, < 2.131.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.security-advisories@github.com ↗
- Before
- Awaiting fix
- After
- Patch available
- ENISA EUVD mappingEUVD-2026-92805 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-92805"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.