https://vulnerability.circl.lu/sightings/feed 2026-10-08T17:23:24.015937+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/be2f24c8-7882-47cd-bdf5-e50a37d42126/export 2026-10-08T17:23:24.043977+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "be2f24c8-7882-47cd-bdf5-e50a37d42126", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-105745", "type": "seen", "source": "https://gist.github.com/alon710/973deaecd942e412a82231dd7cfa7c73", "content": "# CVE-2026-105745: CVE-2026-105745: Arbitrary Code Execution via Malicious Entrypoint Discovery in Docling base_factory\n\n> **CVSS Score:** 6.7\n> **Published:** 2026-10-07\n> **Full Report:** https://cvereports.com/reports/CVE-2026-105745\n\n## Summary\nDocling prior to version 2.131.0 is vulnerable to arbitrary local code execution during module initialization due to incorrect order of operations in its plugin discovery system. Even when the default option to reject external plugins is active, Docling utilizes Pluggy to scan and import entrypoints before performing namespace validation.\n\n## TL;DR\nDocling unconditionally imported external third-party entrypoint modules during initialization before checking namespace validation parameters, allowing malicious local packages to execute code at import time.\n\n## Technical Details\n\n- **CWE ID**: CWE-696\n- **Attack Vector**: Local\n- **CVSS**: 6.7 (Medium)\n- **EPSS Score**: 0.00109\n- **Impact**: Arbitrary Code Execution\n- **Exploit Status**: none\n- **KEV Status**: No\n\n## Affected Systems\n\n- Docling Library (Python Package)\n- Docling Slim (Python Package)\n- **docling**: >= 2.27.0, < 2.131.0 (Fixed in: `2.131.0`)\n- **docling-slim**: >= 2.27.0, < 2.131.0 (Fixed in: `2.131.0`)\n\n## Mitigation\n\n- Upgrade docling to 2.131.0 or newer\n- Restrict site-packages folder write privileges\n- Implement requirements integrity checks with hashes\n- Verify that docling-core is upgraded to 2.98.0 or newer\n\n**Remediation Steps:**\n1. Identify all current python environments utilizing docling.\n2. Run 'pip install --upgrade docling>=2.131.0' to implement the patch.\n3. Execute the provided inspection python script to audit registered entrypoints for compliance.\n4. Ensure virtual environments are locked and unprivileged users cannot write dependency extensions.\n\n## References\n\n- [GHSA-9jxx-vjrv-h2rq Security Advisory](https://github.com/docling-project/docling/security/advisories/GHSA-9jxx-vjrv-h2rq)\n- [Fix Loading Order of External Plugins Pull Request](https://github.com/docling-project/docling/pull/4413)\n- [Security Correction Commit](https://github.com/docling-project/docling/commit/0f443b3786e98688a2da3b7c8f56fe5e46af876c)\n- [Docling v2.131.0 Release Changelog](https://github.com/docling-project/docling/releases/tag/v2.131.0)\n- [NVD Vulnerability Detail Details](https://nvd.nist.gov/vuln/detail/CVE-2026-105745)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-105745) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-10-08T10:30:30.000000Z"} 2026-10-08T10:30:30+00:00