Summary
JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
Description
A Markdown file or a notebook output can carry a button that runs a JupyterLab command. Since 4.5.7 the first click on such a button opens a prompt naming the command, with Cancel, Run Once and Trust. Choosing Trust runs the command and marks the document trusted, so its later buttons run without a prompt.
Which document gets marked is decided when the user answers, not when they click. Both trust commands read whichever document is current at that moment: markdownviewer:trust uses tracker.currentWidget, and notebook:trust uses the equivalent lookup. If another document becomes current while the prompt is open, that document is the one marked trusted, and the one the user was looking at stays untrusted.
Users are affected if all of the following are true:
- they run JupyterLab 4.5.7 through 4.6.3, or an application that bundles it such as Notebook 7.5+;
- they open a Markdown file or notebook from someone else and click a button in it;
- they answer Trust rather than Cancel or Run Once; and
- a second document becomes the current one while the prompt is open, for example through a workspace restoring at startup, an extension activating a widget, or a command that opens a file
Notebooks are written to disk
When the document marked is a notebook, the effect outlives the browser session. notebook:trust marks every cell trusted and then saves the file, which results in the server signing it, so the notebook stays trusted when it is next opened. The save also writes out any unsaved edits in that notebook. A second confirmation appears first, but it says only that a trusted notebook may execute hidden code, without naming the file, so it does not show the user which notebook is about to be trusted.
A Markdown preview marked this way stays trusted only until it is closed. Nothing is written to disk.
Workarounds
Given the high complexity of a potential exploit, we advise treating this as a defense in-depth and update at earliest opportunity, rather than apply the workarounds listed below. However, for users running in highly sensitive environments who are unable to upgrade the workarounds are included below.
Turn off command linker, which removes the ability to execute frontend commands altogether:
{
"@jupyterlab/apputils-extension:sanitizer": {
"allowCommandLinker": false
}
}
In such configuration the buttons in Markdown files and notebook outputs then do nothing when clicked. Documentation and extensions that use command links for navigation stop working, and the setting applies to every document, not only untrusted ones.
If disabling that setting is not desirable and update is not possible, advise users to choose "Run Once" rather than "Trust". "Run Once" makes the command run but no document is marked, so nothing can be trusted in error.
Impact
The user loses control over which document they trusted. Every button in the document that was (incorrectly) marked as trusted runs from then on without a prompt, so if that document also came from an untrusted source, its buttons fire on a single click with no confirmation. That is the state the prompt was added to prevent, in GHSA-mqcg-5x36-vfcg.
The command that ran had the user's consent, because the prompt named it and they pressed Trust. The document they were reading stays untrusted, so it prompts again on the next click.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2026-102832 has a CVSS score of 4.2 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.6.4, 4.5.11, 7.6.3, 0.8.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
JupyterLab v4.6.4 and v4.5.11 contain the patch. The trust request now carries the document that was clicked, and the command is run only once that same document has been marked.
Users of applications that depend on JupyterLab, such as Notebook v7+, should update jupyterlab package too.
Frequently Asked Questions
- What is CVE-2026-102832? CVE-2026-102832 is a medium-severity incorrect authorization vulnerability in jupyterlab (pip), affecting versions >= 4.6.0, <= 4.6.3. It is fixed in 4.6.4, 4.5.11, 7.6.3, 0.8.4. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- How severe is CVE-2026-102832? CVE-2026-102832 has a CVSS score of 4.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-102832?
jupyterlab(pip) (versions >= 4.6.0, <= 4.6.3)notebook(pip) (versions >= 7.5.6, <= 7.6.2)jupyterlite-core(pip) (versions >= 0.7.5, <= 0.8.3)
- Is there a fix for CVE-2026-102832? Yes. CVE-2026-102832 is fixed in 4.6.4, 4.5.11, 7.6.3, 0.8.4. Upgrade to this version or later.
- Is CVE-2026-102832 exploitable, and should I be worried? Whether CVE-2026-102832 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-102832 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-102832?
- Upgrade
jupyterlabto 4.6.4 or later - Upgrade
jupyterlabto 4.5.11 or later - Upgrade
notebookto 7.6.3 or later - Upgrade
jupyterlite-coreto 0.8.4 or later
- Upgrade