Answer in brief
CVE-2026-73416 records a Medium severity vulnerability in jupyterlab: PyPI extension blocklist package-name canonicalization bypass. The current sources do not mark it as known exploited. The current feed maps jupyterlab/jupyterlab (generic), jupyterlab (pip), jupyterlab (pip), jupyterlab (pypi) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-73416 records a Medium severity vulnerability in jupyterlab: PyPI extension blocklist package-name canonicalization bypass. The current sources do not mark it as known exploited. The current feed maps jupyterlab/jupyterlab (generic), jupyterlab (pip), jupyterlab (pip), jupyterlab (pypi) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps jupyterlab/jupyterlab (generic), jupyterlab (pip), jupyterlab (pip), jupyterlab (pypi) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| jupyterlab/jupyterlabgeneric | >= 4.5.0, < 4.5.10 || >= 4.6.0, < 4.6.2 | Not reported |
| jupyterlabpip | >=4.6.0,<=4.6.1 | 4.6.2 |
| jupyterlabpip | >=4.5.0,<=4.5.9 | 4.5.10 |
| jupyterlabpypi | >=4.6.0 <4.6.2 | 4.6.2 |
| jupyterlabpypi | >=4.5.0 <4.5.10 | 4.5.10 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps jupyterlab/jupyterlab (generic), jupyterlab (pip), jupyterlab (pip), jupyterlab (pypi) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| jupyterlab/jupyterlabgeneric | >= 4.5.0, < 4.5.10 || >= 4.6.0, < 4.6.2 | Not reported |
| jupyterlabpip | >=4.6.0,<=4.6.1 | 4.6.2 |
| jupyterlabpip | >=4.5.0,<=4.5.9 | 4.5.10 |
| jupyterlabpypi | >=4.6.0 <4.6.2 | 4.6.2 |
| jupyterlabpypi | >=4.5.0 <4.5.10 | 4.5.10 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.