CVE-2026-102832: JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
JupyterLabto a version that resolves this vulnerability.Fixed in 4.5.11 - Upgrade
Upgrade
JupyterLabto a version that resolves this vulnerability.Fixed in 4.6.4
Event History
Frequently Asked Questions
What conditions are required to trigger the unintended trust decision?
A user must open a trust prompt from a command link, switch so that a different Markdown viewer or notebook becomes the current document while the prompt remains open, and then choose Trust. The second document is trusted instead of the document whose command button was clicked.
What is the impact if a notebook is incorrectly trusted?
Later command buttons in the incorrectly trusted document can run without another prompt. For notebooks, trusting marks all cells trusted, saves any unsaved edits, and persists the server signature to disk.
Which deployments may be affected?
JupyterLab versions from 4.5.7 through 4.5.10 are affected, as is version 4.6.3. Applications that bundle affected JupyterLab releases, including affected Notebook and JupyterLite releases, inherit the behavior.
What versions contain the fix?
The issue is fixed in JupyterLab 4.5.11 and 4.6.4.