# Docling imports plugin entry points before the allow_external_plugins check Advisory record · `GHSA-9jxx-vjrv-h2rq` - **Identifiers:** `GHSA-9jxx-vjrv-h2rq` · `CVE-2026-105745` · `PYSEC-2026-4192` · `PYSEC-2026-4210` - **State:** Confirmed - **Severity:** CVSS 6.7 Medium - **Critical:** No - **Weakness (CWE):** [CWE-696](https://cwe.mitre.org/data/definitions/696.html) · [CWE-829](https://cwe.mitre.org/data/definitions/829.html) - **Tags:** [CWE-696](https://agentprime.io/advisories/tag/cwe-696.md) · [CWE-829](https://agentprime.io/advisories/tag/cwe-829.md) - **Published:** 7 Oct 2026 - **Updated:** 15 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 Oct 2026, 20:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `docling` (PyPI): affected `>=2.27.0, <2.131.0`; fixed in `2.131.0` - `docling-slim` (PyPI): affected `>=2.92.0, <2.131.0`; fixed in `2.131.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Docling versions from 2.27.0 before 2.131.0, and docling-slim versions from 2.92.0 before 2.131.0, import the import-time code of installed third-party plugin modules even when allow_external_plugins is False, which is meant to block them. An attacker who can get a malicious or compromised package with a docling plugin entry point installed into the environment can run code in the docling process. Upgrade docling and docling-slim to 2.131.0. For older versions, install only trusted packages in environments that run docling. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.7 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0012, the 1st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:08 UTC: First seen by agentprime - 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9jxx-vjrv-h2rq) ## Sources - [GitHub Advisory Database: GHSA-9jxx-vjrv-h2rq](https://github.com/advisories/GHSA-9jxx-vjrv-h2rq) - [OSV: GHSA-9jxx-vjrv-h2rq](https://osv.dev/vulnerability/GHSA-9jxx-vjrv-h2rq) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .