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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.2 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N | 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
Sources
- GitHub Advisory Database: GHSA-jwrc-gm9j-263p
- OSV: GHSA-jwrc-gm9j-263p
- github.com/jupyterlab/jupyterlab/security/advisories/GHSA-jwrc-gm9j-263p
- nvd.nist.gov/vuln/detail/CVE-2026-102832
- github.com/jupyterlab/jupyterlab/commit/0fc18ab4ef67e431a8f6560e387193baf786c70a
- github.com/jupyterlab/jupyterlab/commit/b64bc88b8ca034cf158604a5cc48ca9170ea453b
- github.com/jupyterlab/jupyterlab/commit/f7e5f9803fdf2aaaa0e9bfb9cc73386a8cc5f0b2
- github.com/jupyterlab/jupyterlab
- github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11
- github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4