Vulnerability in Jupyterlab

CVE-2026-73416

jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 4.5.0 until 4.5.10 and 4.6.2, in jupyterlab/extensions/manager.py and jupyterlab/extensions/pypi.py, JupyterLab's PyPI extension manager enforces blocked_extensions_uris by comparing requested install names to blocklist entries with custom 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, and JupyterLab accepts the install request even though pip resolves the variant to the same package. Security impact requires an allowlist or blocklist intended to restrict package installation, the PyPI Extension Manager, and kernels and terminals that are disabled or delegated to remote hosts. The bypass lets an authenticated user install a prohibited extension, defeat integrity restrictions, and affect availability without gaining new read access. This issue is fixed in versions 4.5.10 and 4.6.2.

Published · last modified .

EPSS exploit prediction

EPSS: 0.007 (49.7th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 50th percentile — 49.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-73416: held from 0.005 to 0.007.

EPSS over last 30 days · oldest: 0.005 · newest: 0.007 · change: +0.002

Affected products

  • Jupyterlab — versions >= 4.5.0, < 4.5.10, >= 4.6.0, < 4.6.2

Weakness classification (CWE)

References