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

Published Oct 13, 2026
·
Updated

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

1 affected component
jupyter JupyterLab>=4.5.7<4.5.11, >=4.6.0<4.6.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 4.5.11
  2. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 4.6.4

Event History

Oct 13, 2026
CVE Published
via MITRE·03:19 PM
Data Sourced
via MITRE·03:19 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

What versions contain the fix?

The issue is fixed in JupyterLab 4.5.11 and 4.6.4.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203