GitHub Advisoryadvisory · PyPI

GHSA-h5v5-8746-g7mm JupyterLab PluginManager lock-rule enforcement bypass

MEDIUM Published 2026-07-22 Modified 2026-07-22 Official page ↗
Ecosystem
PyPI
Packages
jupyterlab
Severity
Moderate
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Weaknesses
CWE-602, CWE-863
Reviewed
2026-07-22

Affected packages

• PyPI jupyterlab: >= 4.6.0, < 4.6.2 → fixed in 4.6.2 • PyPI jupyterlab: >= 4.1.0, < 4.5.10 → fixed in 4.5.10

Description

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: • child plugins of extensions covering multiple plugins • when "lock all" was issued by the administrator 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.

Related

Weakness · CWE (2)

  • CWE-602 Client-Side Enforcement of Server-Side Security weakness
  • CWE-863 Incorrect Authorization weakness

References