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

Severity: medium (CVSS 4.2 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-10-13 · updated 2026-10-16
Weakness: CWE-367

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.

Affected products

jupyterlab: from 4.5.7, < 4.5.11; from 4.6.0, < 4.6.4
jupyterlab jupyterlite-core: from 0.7.5, < 0.8.4
jupyter notebook: from 7.5.6, < 7.6.3

References

Get alerted when CVE-2026-102832 or the next vulnerability affects your stack