Skip to main content
← All vulnerabilities
CVE-2026-102832GHSA-JWRC-GM9J-263P

JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.5.11, 4.6.4, 0.8.4, 7.6.3
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • jupyterlab 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

  • jupyterlabPyPI

    From 4.6.0 · fixed in 4.6.4

  • jupyterlabPyPI

    From 4.5.7 · fixed in 4.5.11

  • notebookPyPI

    From 7.5.6 · fixed in 7.6.3

  • jupyterlite-corePyPI

    From 0.7.5 · fixed in 0.8.4

References 6

GitHub · jupyterlab/jupyterlab