CVE-2026-73627: JupyterLab 4.6.0 Plugin Manager Lock-Rule Enforcement Bypass
JupyterLab (pip package 'jupyterlab') versions >=4.1.0,<=4.5.9 and >=4.6.0,<=4.6.1 contain a plugin manager lock-rule enforcement bypass. Two server-side enforcement gaps allow an authenticated user to circumvent administrator lock rules by making direct requests to the /lab/api/plugins endpoint, enabling or disabling plugins that were locked — including child plugins of multi-plugin extensions and plugins locked via the 'lock all' mechanism. This can impact data integrity and bypass hardening or restrictions (e.g., download/upload limits) implemented through locked plugins. Fixed in versions 4.6.2 and 4.5.10.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
jupyterlab (pip package)to a version that resolves this vulnerability.Fixed in 4.6.2 - Upgrade
Upgrade
jupyterlab (pip package)to a version that resolves this vulnerability.Fixed in 4.5.10
Event History
Frequently Asked Questions
What is the severity of CVE-2026-73627?
CVE-2026-73627 has a risk score of 40, indicating a moderate severity vulnerability.
How do I fix CVE-2026-73627?
To mitigate CVE-2026-73627, upgrade JupyterLab to version 4.6.2 or later.
Which versions of JupyterLab are affected by CVE-2026-73627?
CVE-2026-73627 affects JupyterLab versions from 4.1.0 to 4.5.9 and 4.6.0 to 4.6.1.
What kind of vulnerability is CVE-2026-73627?
CVE-2026-73627 is a plugin manager lock-rule enforcement bypass vulnerability.
Who can exploit CVE-2026-73627?
An authenticated user can exploit CVE-2026-73627 to bypass administrator lock rules.