jupyterlab
Affected
- introduced
4.0.0, fixed4.5.7(ecosystem)
Fixed versions
4.5.7
Fix
- Fixed version
4.5.7pip install --upgrade jupyterlab==4.5.7
Advisory
Also known as: BIT-jupyterlab-2026-42266, CVE-2026-42266, PYSEC-2026-164
JupyterLab has an Extension Manager API/GUI Policy Discrepancy, allowing 3rd party (malicious) extensions install via POST request
The allow-list of extensions that can be installed from PyPI Extension Manager (allowed_extensions_uris) is not correctly enforced by JupyterLab prior to 4.5.7. The PyPI Extension Manager was not contained to packages listed on the default PyPI index.
This has security implications for deployments that:
Impact
An authenticated attacker - such as a student in a shared JupyterHub environment or a user in a multi-tenant JupyterLab deployment - can escalate their privileges. This might allow for data exfiltration, lateral movement within the network, and persistent compromise of the server infrastructure.
Patches
JupyterLab `v4.5.7` contains the patch.
Users of applications that depend on JupyterLab, such as Notebook v7+, should update jupyterlab package too.
Workarounds
Switch to read-only extension manager by adding the following command line option:
--LabApp.extension_manager=readonly
or the following traitlet:
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" />
Note: configuration of a PyPI proxy with allow-listed packages is not sufficient to protect from this vulnerability.
References
High Basis: The source's own band: HIGH
4.0.0, fixed 4.5.7 (ecosystem)4.5.7
4.5.7pip install --upgrade jupyterlab==4.5.7Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0