GHSA-whvh-wf3x-g77j: JupyterLab Remote Code Execution Vulnerability

LOW
CVSS 0.0
CWE-284 CWE-636
Published
Advisory Summary

GHSA-whvh-wf3x-g77j is a LOW (CVSS 0.0) remote code execution vulnerability (CWE-284: Improper Access Control) affecting JupyterLab libraries in the PyPI ecosystem. The issue involves allowlist/blocklist check in `pypiextensionmanager.install()` not enforced for direct callers (missing `await`). Remediation is available by upgrading affected packages to version 4.6.2, 4.5.10.

GHSA-whvh-wf3x-g77j at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-whvh-wf3x-g77j
Severity LOW
CVSS v3.1 Base Score 0.0
CWE Classification CWE-284: Improper Access Control
Affected Product JupyterLab
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 0.0

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

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

How to Fix GHSA-whvh-wf3x-g77j

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.2
pip install jupyterlab>=4.6.2
jupyterlab fixed: 4.5.10
pip install jupyterlab>=4.5.10
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 GHSA-whvh-wf3x-g77j, 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.2), 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-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. 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

The extension allowlist/blocklist check inside `PyPIExtensionManager.install()` was not enforced due to a missing await. For purposes of JupyterLab this was a secondary defense-in-depth check: `install()` was intended to enforce the allowlist/blocklist itself for any future uses and users calling this method directly (in addition to the separate check handling requests arriving through the HTTP API). The only runtime symptom was a `RuntimeWarning: coroutine 'is_install_allowed' was never awaited.` This has security implications only for deployments that combine all of the following: - a custom extension or downstream integration that imports `PyPIExtensionManager` and calls `install()` directly with a package name influenced by untrusted user input (the stock JupyterLab HTTP handler is not affected - it performs its own awaited allowlist check before calling `install()`); - an allowlist/blocklist configured with the intent of restricting which packages users can install; - the (default) PyPI Extension Manager enabled; and - kernels and terminals disabled or delegated to remote hosts, so that the custom extension's `install()` call is the only available package-install vector (otherwise a user with kernel access can install packages directly regardless of this check) ### Impact Low. No exposure for stock JupyterLab: the HTTP API and Extension Manager UI enforce the listing through a separate, correctly awaited check. The gap affected only custom extensions or downstream integrations that called the public `install()` method directly and relied on it to self-enforce. ### Patches JupyterLab [`v4.6.2`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2) and [`v4.5.10`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10) contain the patch. Users of applications that depend on JupyterLab, such as Notebook v7+, should update `jupyterlab` package too. ### Workarounds No action is required for deployments that only expose extension management through the JupyterLab HTTP API / Extension Manager UI, as that path was already enforcing the listing via the handler's own check. Deployments wanting to disable programmatic extension installation entirely can switch to the read-only extension manager: ```bash --LabApp.extension_manager=readonly ``` or the following traitlet: ```python c.LabApp.extension_manager = 'readonly' ``` You can confirm that the read-only manager is in use from GUI: <img width="293" height="293" alt="image" src="https://github.com/user-attachments/assets/8016c809-633e-4ed0-a5bc-6bc4793caa0f" />

GHSA-whvh-wf3x-g77j Affected JupyterLab Versions

2 component(s)
Fixed Versions:
4.6.24.5.10
Product / Package Ecosystem Affected Versions Fixed Version
jupyterlab
PyPI
≥ 4.6.0
< 4.6.2
4.6.2
jupyterlab
PyPI
< 4.5.10
4.5.10

References

Frequently Asked Questions

What is GHSA-whvh-wf3x-g77j?
GHSA-whvh-wf3x-g77j is a security vulnerability in JupyterLab involving Allowlist/blocklist check in `PyPIExtensionManager.install()` not enforced for direct callers (missing `await`) under CWE-284: Improper Access Control.
Which JupyterLab versions are affected?
Affected versions include releases prior to 4.6.2, 4.5.10 across affected packages: jupyterlab.
What version fixes GHSA-whvh-wf3x-g77j?
Upgrading to 4.6.2, 4.5.10 (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.2, 4.5.10. Upgrade your dependency to 4.6.2, 4.5.10 or later.
What is the CVSS score of GHSA-whvh-wf3x-g77j?
GHSA-whvh-wf3x-g77j has a CVSS v3.1 base score of 0.0 (LOW) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N.
What CWE is associated with GHSA-whvh-wf3x-g77j?
GHSA-whvh-wf3x-g77j is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check PyPI dependencies for GHSA-whvh-wf3x-g77j?
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-whvh-wf3x-g77j",
  "modified" : "2026-07-22T23:12:22Z",
  "published" : "2026-07-22T23:12:22Z",
  "aliases" : [ ],
  "summary" : "JupyterLab: Allowlist/blocklist check in `PyPIExtensionManager.install()` not enforced for direct callers (missing `await`)",
  "details" : "The extension allowlist/blocklist check inside `PyPIExtensionManager.install()` was not enforced due to a missing await. For purposes of JupyterLab this was a secondary defense-in-depth check: `install()` was intended to enforce the allowlist/blocklist itself for any future uses and users calling this method directly (in addition to the separate check handling requests arriving through the HTTP API).  The only runtime symptom was a `RuntimeWarning: coroutine 'is_install_allowed' was never awaited.`\n\nThis has security implications only for deployments that combine all of the following:\n- a custom extension or downstream integration that imports `PyPIExtensionManager` and calls `install()` directly with a package name influenced by untrusted user input (the stock JupyterLab HTTP handler is not affected - it performs its own awaited allowlist check before calling `install()`);\n- an allowlist/blocklist configured with the intent of restricting which packages users can install;\n- the (default) PyPI Extension Manager enabled; and\n- kernels and terminals disabled or delegated to remote hosts, so that the custom extension's `install()` call is the only available package-install vector (otherwise a user with kernel access can install packages directly regardless of this check)\n\n### Impact\n\nLow. No exposure for stock JupyterLab: the HTTP API and Extension Manager UI enforce the listing through a separate, correctly awaited check. The gap affected only custom extensions or downstream integrations that called the public `install()` method directly and relied on it to self-enforce.\n\n### Patches\n\nJupyterLab [`v4.6.2`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2) and [`v4.5.10`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10) contain the patch.\n\nUsers of applications that depend on JupyterLab, such as Notebook v7+, should update `jupyterlab` package too.\n\n### Workarounds\n\nNo action is required for deployments that only expose extension management through the JupyterLab HTTP API / Extension Manager UI, as that path was already enforcing the listing via the handler's own check. Deployments wanting to disable programmatic extension installation entirely can switch to the read-only extension manager:\n\n```bash\n--LabApp.extension_manager=readonly\n```\n\nor the following traitlet:\n\n```python\nc.LabApp.extension_manager = 'readonly'\n```\n\nYou can confirm that the read-only manager is in use from GUI:\n\n<img width=\"293\" height=\"293\" alt=\"image\" src=\"https://github.com/user-attachments/assets/8016c809-633e-4ed0-a5bc-6bc4793caa0f\" />",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlab"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.6.0"
      }, {
        "fixed" : "4.6.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.6.1"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlab"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.5.10"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.5.9"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-whvh-wf3x-g77j"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/pull/19184"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/pull/19185"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/pull/19186"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/be9303f5bcd5308eaeae953c5a3c903046682c2c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/f1beab4a2027af4719d6edc07d52d6cf5a39a432"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jupyterlab/jupyterlab"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-284", "CWE-636" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T23:12:22Z",
    "nvd_published_at" : null
  }
}