Vulnerabilities in pkg:pypi/jupyterlab

PACKAGE
Advisory Identifier: GHSA-jwrc-gm9j-263p
Advisory Summary

CVE-2026-102832 is a MODERATE (CVSS 4.2) command link trust prompt vulnerability (CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition) affecting JupyterLab libraries in the PyPI ecosystem. The issue involves command link trust prompt in jupyterlab can trust a document other than the one clicked. Remediation is available by upgrading affected packages to version 4.6.4, 4.5.11, 7.6.3, 0.8.4.

18 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/jupyterlab

18 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/jupyterlab. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-jwrc-gm9j-263p CVE-2026-102832 MODERATE JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
GHSA-3jqq-pw4j-pqcj CVE-2026-102830 MODERATE JupyterLab: Cross-site scripting (XSS) in JupyterLab via crafted language package (jupyterlab.json)
GHSA-3325-v43h-43rv CVE-2026-102904 MODERATE JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs
GHSA-6966-vjj6-99xv CVE-2026-102831 HIGH JupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboard
GHSA-pppj-hq3g-57pj CVE-2026-73417 HIGH JupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)
GHSA-89vp-jrxv-24w8 CVE-2026-73416 MODERATE JupyterLab: PyPI extension blocklist package-name canonicalization bypass
GHSA-gx64-gj6p-pc4c CVE-2026-73415 HIGH JupyterLab: Image viewer allows XSS when opening malicious image in new browser tab
GHSA-h5v5-8746-g7mm - MODERATE JupyterLab PluginManager lock-rule enforcement bypass
GHSA-whvh-wf3x-g77j - LOW JupyterLab: Allowlist/blocklist check in `PyPIExtensionManager.install()` not enforced for direct callers (missing `await`)
GHSA-vmhf-c436-hxj4 - MODERATE JupyterLab: Stored XSS in extension manager through package metadata unsanitized URI protocol
GHSA-mqcg-5x36-vfcg CVE-2026-42557 HIGH JupyterLab's command linker attributes in HTML enable one-click command execution from untrusted content
GHSA-37w4-hwhx-4rc4 CVE-2026-42266 HIGH JupyterLab has an Extension Manager API/GUI Policy Discrepancy, allowing 3rd party (malicious) extensions install via POST request
GHSA-rch3-82jr-f9w9 CVE-2026-40171 HIGH Jupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSS
GHSA-vvfj-2jqx-52jm CVE-2025-59842 LOW JupyterLab LaTeX typesetter links did not enforce `noopener` attribute
GHSA-4952-p58q-6crx CVE-2021-32797 MODERATE JupyterLab: XSS due to lack of sanitization of the action attribute of an html <form>
GHSA-9q39-rmj3-p4r2 CVE-2024-43805 HIGH HTML injection in Jupyter Notebook and JupyterLab leading to DOM Clobbering
GHSA-4m77-cmpx-vjc4 CVE-2024-22420 MODERATE JupyterLab vulnerable to SXSS in Markdown Preview
GHSA-44cc-43rp-5947 CVE-2024-22421 HIGH JupyterLab vulnerable to potential authentication and CSRF tokens leak

CVE-2026-102832 at a Glance

CVE Identifier CVE-2026-102832
GHSA Identifier GHSA-jwrc-gm9j-263p
Severity MODERATE
CVSS v3.1 Base Score 4.2
CWE Classification CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
Affected Product JupyterLab
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 4.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-102832

To remediate this vulnerability, upgrade all affected JupyterLab dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

jupyterlab fixed: 4.6.4
pip install jupyterlab>=4.6.4
jupyterlab fixed: 4.5.11
pip install jupyterlab>=4.5.11
notebook fixed: 7.6.3
pip install notebook>=7.6.3
jupyterlite-core fixed: 0.8.4
pip install jupyterlite-core>=0.8.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show jupyterlab

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-102832, inspect your installed packages using pip:

pip show jupyterlab

Analyze the terminal output to locate any version of JupyterLab in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.6.4), your application is affected.

Note: The pip show jupyterlab command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition, where the product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. In JupyterLab, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 ### 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. `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. ### Patches JupyterLab [`v4.6.4`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4) and [`v4.5.11`](https://github.com/jupyterlab/jupyterlab/releases/tag/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. ### 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: ```json { "@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.

CVE-2026-102832 Affected JupyterLab Versions

4 component(s)
Fixed Versions:
4.6.44.5.117.6.30.8.4
Product / Package Ecosystem Affected Versions Fixed Version
jupyterlab
PyPI
≥ 4.6.0
< 4.6.4
4.6.4
jupyterlab
PyPI
≥ 4.5.7
< 4.5.11
4.5.11
notebook
PyPI
≥ 7.5.6
< 7.6.3
7.6.3
jupyterlite-core
PyPI
≥ 0.7.5
< 0.8.4
0.8.4

References

Frequently Asked Questions

What is CVE-2026-102832?
CVE-2026-102832 is a security vulnerability in JupyterLab involving Command link trust prompt in JupyterLab can trust a document other than the one clicked under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition.
Which JupyterLab versions are affected?
Affected versions include releases prior to 4.6.4, 4.5.11, 7.6.3, 0.8.4 across affected packages: jupyterlab, notebook, jupyterlite-core.
What version fixes CVE-2026-102832?
Upgrading to 4.6.4, 4.5.11, 7.6.3, 0.8.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is jupyterlab affected?
Yes, jupyterlab is affected in releases prior to 4.6.4, 4.5.11. Upgrade your dependency to 4.6.4, 4.5.11 or later.
Is notebook affected?
Yes, notebook is affected in releases prior to 7.6.3. Upgrade your dependency to 7.6.3 or later.
What is the CVSS score of CVE-2026-102832?
CVE-2026-102832 has a CVSS v3.1 base score of 4.2 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-102832?
CVE-2026-102832 is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition (The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.).
How can I check PyPI dependencies for CVE-2026-102832?
Run the dependency tree command: 'pip show jupyterlab'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jwrc-gm9j-263p",
  "modified" : "2026-10-15T20:22:13Z",
  "published" : "2026-10-15T20:22:13Z",
  "aliases" : [ "CVE-2026-102832" ],
  "summary" : "JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked",
  "details" : "## Description\n\nA 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.\n\nWhich 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.\n\nUsers are affected if all of the following are true:\n\n- they run JupyterLab 4.5.7 through 4.6.3, or an application that bundles it such as Notebook 7.5+;\n- they open a Markdown file or notebook from someone else and click a button in it;\n- they answer Trust rather than Cancel or Run Once; and\n- 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\n\n### Impact\n\nThe 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).\n\nThe 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.\n\n#### Notebooks are written to disk\n\nWhen 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.\n\nA Markdown preview marked this way stays trusted only until it is closed. Nothing is written to disk.\n\n### Patches\n\nJupyterLab [`v4.6.4`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4) and [`v4.5.11`](https://github.com/jupyterlab/jupyterlab/releases/tag/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.\n\nUsers of applications that depend on JupyterLab, such as Notebook v7+, should update `jupyterlab` package too.\n\n### Workarounds\n\nGiven 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. \n\nTurn off command linker, which removes the ability to execute frontend commands altogether:\n\n```json\n{\n  \"@jupyterlab/apputils-extension:sanitizer\": {\n    \"allowCommandLinker\": false\n  }\n}\n```\n\nIn 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.\n\nIf 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlab"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.6.0"
      }, {
        "fixed" : "4.6.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.6.3"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlab"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.5.7"
      }, {
        "fixed" : "4.5.11"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.5.10"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "notebook"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.5.6"
      }, {
        "fixed" : "7.6.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 7.6.2"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlite-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.7.5"
      }, {
        "fixed" : "0.8.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.8.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-jwrc-gm9j-263p"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-102832"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/0fc18ab4ef67e431a8f6560e387193baf786c70a"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/b64bc88b8ca034cf158604a5cc48ca9170ea453b"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/f7e5f9803fdf2aaaa0e9bfb9cc73386a8cc5f0b2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jupyterlab/jupyterlab"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-367", "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T20:22:13Z",
    "nvd_published_at" : "2026-10-13T16:17:09Z"
  }
}