# JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked Advisory record · `GHSA-jwrc-gm9j-263p` - **Identifiers:** `GHSA-jwrc-gm9j-263p` · `CVE-2026-102832` - **State:** Confirmed - **Severity:** CVSS 4.2 Medium - **Critical:** No - **Weakness (CWE):** [CWE-367](https://cwe.mitre.org/data/definitions/367.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html) - **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 15 Oct 2026 - **Updated:** 15 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 15 Oct 2026, 20:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `jupyterlab` (PyPI): affected `>=4.6.0, <4.6.4 || >=4.5.7, <4.5.11`; fixed in `4.6.4`, `4.5.11` - `notebook` (PyPI): affected `>=7.5.6, <7.6.3`; fixed in `7.6.3` - `jupyterlite-core` (PyPI): affected `>=0.7.5, <0.8.4`; fixed in `0.8.4` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > JupyterLab versions 4.5.7 through 4.5.10 and 4.6.0 through 4.6.3 are affected, along with notebook 7.5.6 through 7.6.2 and jupyterlite-core 0.7.5 through 0.8.3. When a user clicks a command link in an untrusted Markdown file or notebook and chooses Trust, the trust may be applied to a different document that became current while the prompt was open, so that document's buttons later run without a prompt. Upgrade jupyterlab to 4.5.11 or 4.6.4, notebook to 7.6.3, or jupyterlite-core to 0.8.4. Choosing Run Once instead of Trust avoids the problem until upgrading. 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 - 4.2 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0014, the 3rd 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-jwrc-gm9j-263p) ## Sources - [GitHub Advisory Database: GHSA-jwrc-gm9j-263p](https://github.com/advisories/GHSA-jwrc-gm9j-263p) - [OSV: GHSA-jwrc-gm9j-263p](https://osv.dev/vulnerability/GHSA-jwrc-gm9j-263p) - - - - - - - - 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: .