jupyterlab
Affected
- introduced
4.6.0, fixed4.6.2(ecosystem)
Fixed versions
4.6.2
Fix
- Fixed version
4.6.2pip install --upgrade jupyterlab==4.6.2
Advisory
Also known as: BIT-jupyterlab-2026-73627, CVE-2026-73627
JupyterLab PluginManager lock-rule enforcement bypass
JupyterLab's plugin manager exposes administrator controls intended to prevent users from enabling or disabling selected plugins. Two server-side enforcement gaps let an authenticated user bypass those controls with direct requests to /lab/api/plugins.
Impact
Users could workaround the plugin manager lock rules via direct API access for either:
The integrity of data can be impacted, and any hardening or restrictions on permitted user actions (e.g. download/upload limits) within the single-user server can be circumvented if those were implemented with plugins that were locked using the faulty mechanisms.
Patches
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.
Workarounds
Manually lock all plugins that should be locked. The core plugin identifiers can be found in the documentation and identifiers for all installed extensions are listed in the Plugin Manager.
Medium Basis: The source's own band: MODERATE
4.6.0, fixed 4.6.2 (ecosystem)4.6.2
4.6.2pip install --upgrade jupyterlab==4.6.24.1.0, fixed 4.5.10 (ecosystem)4.5.10
4.5.10pip install --upgrade jupyterlab==4.5.10Fix 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