Vulnerability · CVE-2026-102832
JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
Published Oct 13, 2026 · catalog updated Oct 15, 2026 · JupyterLab: Command link trust
Check if you run it
No confirmed exploitation is on record for CVE-2026-102832. EPSS is 0.14%. Act only if a listed version of JupyterLab: Command link trust is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (JupyterLab: Command link trust).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium4.2
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.14%
- Remediation
- Version ranges on file
- Affected products
- PyPI jupyterlab · PyPI jupyterlite-core · PyPI notebook · pip jupyterlab · pip jupyterlite-core · pip notebook
## 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: uses , and 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 ### 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](https://github.com/jupyterlab/jupyterlab/security/advisories/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. #### Notebooks are written to disk When the document marked is a notebook, the effect outlives the browser session. marks every cell trusted and then saves the file, which results in the server signing it, so the note
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- PyPI jupyterlab4.5.7 → 4.5.11
- PyPI jupyterlab4.6.0 → 4.6.4
- PyPI jupyterlite-core0.7.5 → 0.8.4
- PyPI notebook7.5.6 → 7.6.3
- pip jupyterlab>= 4.5.7, <= 4.5.10
- pip jupyterlab>= 4.6.0, <= 4.6.3
- pip jupyterlite-core>= 0.7.5, <= 0.8.3
- pip notebook>= 7.5.6, <= 7.6.2
- pypi jupyterlabversion unspecified
- pypi jupyterlite-coreversion unspecified
- pypi notebookversion unspecified
- vendor jupyterlab jupyterlabversion unspecified
- vendor jupyterlab jupyterlite-coreversion unspecified
- vendor jupyterlab notebookversion unspecified
How to fix CVE-2026-102832
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-102832. EPSS is 0.14%. Act only if a listed version of JupyterLab: Command link trust is installed.
Which versions are affected?
Compare what you have installed with 4.5.7 → 4.5.11, 4.6.0 → 4.6.4, 0.7.5 → 0.8.4, 7.5.6 → 7.6.3, >= 4.5.7, <= 4.5.10, >= 4.6.0, <= 4.6.3. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition; CWE-863: Incorrect Authorization. EPSS 0.14%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 15, 2026 · GitHub Advisory Database
Detected
## 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 cl
Oct 15, 2026 · GitHub Advisory Database
Fix available
jupyterlab fixed in 4.6.4; jupyterlab fixed in 4.5.11; notebook fixed in 7.6.3; jupyterlite-core fixed in 0.8.4
Oct 15, 2026 · GitHub Advisory Database
Fix available
jupyterlab fixed in 4.6.4
Oct 15, 2026 · GitHub Advisory Database
Fix available
jupyterlab fixed in 4.5.11
Oct 15, 2026 · GitHub Advisory Database
Fix available
notebook fixed in 7.6.3
Oct 15, 2026 · GitHub Advisory Database
Fix available
jupyterlite-core fixed in 0.8.4
Oct 15, 2026 · GitHub Advisory Database
Updated
## 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 cl
Sources
- CVE.orgVulnerability recordCVE-2026-102832
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 Ma
cve.org - FIRST EPSSExploitation probabilityCVE-2026-102832
30-day exploitation probability 0.1%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-jwrc-gm9j-263p
JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-102832
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 …
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-jwrc-gm9j-263p
JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
osv.dev - PyPA Advisory DatabasePackage advisoryGHSA-jwrc-gm9j-263p
JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
osv.dev
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.