CVE-2026-73416: JupyterLab PyPI Extension Blocklist Package-name Canonicalization Vulnerability

MODERATE
Advisory Identifier: GHSA-89vp-jrxv-24w8
CWE-180 CWE-178
Published
Advisory Summary

CVE-2026-73416 is a MODERATE pypi extension blocklist package-name canonicalization vulnerability (CWE-180: Incorrect Behavior Order: Validate Before Canonicalize) affecting JupyterLab libraries in the PyPI ecosystem. The issue involves pypi extension blocklist package-name canonicalization bypass. Remediation is available by upgrading affected packages to version 4.6.2, 4.5.10.

CVE-2026-73416 at a Glance

CVE Identifier CVE-2026-73416
GHSA Identifier GHSA-89vp-jrxv-24w8
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-180: Incorrect Behavior Order: Validate Before Canonicalize
Affected Product JupyterLab
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2026-73416

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 CVE-2026-73416, 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-180: Incorrect Behavior Order: Validate Before Canonicalize, where the product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step. 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

JupyterLab's PyPI extension manager enforces `blocked_extensions_uris` by comparing the requested install name to blocklist entries with a custom string normalization that is weaker than PyPI package-name canonicalization. An authenticated user can request a PyPI-equivalent spelling such as `JupyterLab.Git` for a blocklisted package such as `jupyterlab-git`; JupyterLab accepts the install request even though pip resolves the variant to the same package. This has security implications only for deployments that combine all of the following: - 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 (otherwise a user with kernel access can install packages directly regardless of this check) ### Impact The vulnerability lets an authenticated user install a package the operator specifically intended to block, defeating the allowlist/blocklist control. Because extensions in principle allow for arbitrary code execution, this vulnerability enables untrusted users to impact the integrity and availability of the jupyter-server instance that was provisioned to them. The user already has access to their own single-user server's data, so installing an extension grants no new read access. In particular, the integrity of data can be impacted, and any hardening or restrictions on permitted user actions (download/upload limits) within the single-user server can be circumvented. Availability impact on a JupyterHub deployment is limited: while a user can be expected to exhaust their own kernel pod's resources, this vulnerability makes it easier to also exhaust the single-user server resources or generate more requests to shared resources; where limits are absent, resource exhaustion could potentially degrade the wider deployment. ### 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 do not have a custom allow/block list configured. 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" />

CVE-2026-73416 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.0
< 4.5.10
4.5.10

References

Frequently Asked Questions

What is CVE-2026-73416?
CVE-2026-73416 is a security vulnerability in JupyterLab involving PyPI extension blocklist package-name canonicalization bypass under CWE-180: Incorrect Behavior Order: Validate Before Canonicalize.
Which JupyterLab versions are affected?
Affected versions include releases prior to 4.6.2, 4.5.10 across affected packages: jupyterlab.
What version fixes CVE-2026-73416?
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 CWE is associated with CVE-2026-73416?
CVE-2026-73416 is classified under CWE-180: Incorrect Behavior Order: Validate Before Canonicalize (The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.).
How can I check PyPI dependencies for CVE-2026-73416?
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-89vp-jrxv-24w8",
  "modified" : "2026-08-12T19:56:08Z",
  "published" : "2026-07-22T23:14:27Z",
  "aliases" : [ "CVE-2026-73416" ],
  "summary" : "JupyterLab: PyPI extension blocklist package-name canonicalization bypass",
  "details" : "JupyterLab's PyPI extension manager enforces `blocked_extensions_uris` by comparing the requested install name to blocklist entries with a custom string normalization that is weaker than PyPI package-name canonicalization. An authenticated user can request a PyPI-equivalent spelling such as `JupyterLab.Git` for a blocklisted package such as `jupyterlab-git`; JupyterLab accepts the install request even though pip resolves the variant to the same package.\n\nThis has security implications only for deployments that combine all of the following:\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 (otherwise a user with kernel access can install packages directly regardless of this check) \n\n### Impact\n\nThe vulnerability lets an authenticated user install a package the operator specifically intended to block, defeating the allowlist/blocklist control. Because extensions in principle allow for arbitrary code execution, this vulnerability enables untrusted users to impact the integrity and availability of the jupyter-server instance that was provisioned to them. The user already has access to their own single-user server's data, so installing an extension grants no new read access.\n\nIn particular, the integrity of data can be impacted, and any hardening or restrictions on permitted user actions (download/upload limits) within the single-user server can be circumvented. Availability impact on a JupyterHub deployment is limited: while a user can be expected to exhaust their own kernel pod's resources, this vulnerability makes it easier to also exhaust the single-user server resources or generate more requests to shared resources; where limits are absent, resource exhaustion could potentially degrade the wider deployment.\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 do not have a custom allow/block list configured. 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_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA: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" : "4.5.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-89vp-jrxv-24w8"
  }, {
    "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-178", "CWE-180" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T23:14:27Z",
    "nvd_published_at" : null
  }
}