JupyterLab: PyPI extension blocklist package-name canonicalization bypass
CVE-2026-73416 · GHSA-89vp-jrxv-24w8 · published 2026-07-22 · updated 2026-08-12
- Severity
- Medium
- CVSS score
- 6.1
- Chance of exploitation (EPSS)
- 0.66%
- Fixed in
- 4.6.2
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade jupyterlab to 4.6.2 or later.
JupyterLab v4.6.2 and v4.5.10 contain the patch. Users of applications that depend on JupyterLab, such as Notebook v7+, should update jupyterlab package too.
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: or the following traitlet: You can confirm that the read-only manager is in use from GUI:
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| jupyterlab | PyPI | >= 4.5.0, <= 4.5.9 | 4.5.10 |
| jupyterlab | PyPI | >= 4.6.0, <= 4.6.1 | 4.6.2 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- HighJupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboardjupyterlab, jupyterlab, notebook
- HighJupyterLab: Image viewer allows XSS when opening malicious image in new browser tabjupyterlab, jupyterlab
- HighJupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)jupyterlab, jupyterlab
- HighJupyterLab's command linker attributes in HTML enable one-click command execution from untrusted contentjupyterlab, notebook
- HighJupyterLab has an Extension Manager API/GUI Policy Discrepancy, allowing 3rd party (malicious) extensions install via POST requestjupyterlab
- HighJupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSSjupyterlab, notebook
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.