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

Medium 4.2 Published Updated

Attackers can bypass trust prompts by switching documents during confirmation, allowing untrusted code execution in JupyterLab.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-102832?

CVE-2026-102832 is a medium-severity vulnerability in jupyterlab, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-863, CWE-367

Which versions are affected by CVE-2026-102832?

8 open source packages ship an affected version, including jupyterlab, jupyterlite-core and notebook.

PackageAffectedFixed in
jupyterlab PyPIFrom 4.5.74.5.11
jupyterlab PyPIFrom 4.5.74.5.11
jupyterlab PyPIFrom 4.6.04.6.4
jupyterlab PyPIFrom 4.6.04.6.4
jupyterlite-core PyPIFrom 0.7.50.8.4
jupyterlite-core PyPIFrom 0.7.50.8.4
2 more packages
notebook PyPIFrom 7.5.67.6.3
notebook PyPIFrom 7.5.67.6.3

How do I fix CVE-2026-102832?

Upgrade jupyterlab to a fixed version for your release line: 4.5.11 or 4.6.4.

Is CVE-2026-102832 being exploited?

There is no known exploitation of CVE-2026-102832 in the wild and no public exploit code.

Sources

Also known as GHSA-jwrc-gm9j-263p, MINI-55w7-x268-8h65, MINI-w2jj-869g-mh6x, UBUNTU-CVE-2026-102832.

Is CVE-2026-102832 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free