https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 18:43:52 +0000 https://vulnerability.circl.lu/vuln/brew-jupyterlab-ghsa-h5v5-8746-g7mm <p><strong>Affected:</strong> Homebrew: jupyterlab</p> <p>JupyterLab&#39;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`.</p> <p>### Impact</p> <p>Users could workaround the plugin manager lock rules via direct API access for either: - child plugins of extensions covering multiple plugins - when &#34;lock all&#34; was issued by the administrator</p> <p>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.</p> <p>### Patches</p> <p>JupyterLab [`v4.6.2`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2) and [`v4.5.10`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10) contain the patch.</p> <p>Users of applications that depend on JupyterLab, such as Notebook v7+, should update `jupyterlab` package too.</p> <p>### Workarounds</p> <p>Manually lock all plugins that should be locked. The core plugin identifiers can be found in [the documentation](https://jupyterlab.readthedocs.io/en/latest/extension/extension_points.html#core-plugins) and identifiers for all installed extensions are listed in the [Plugin Manager](https://jupyterlab.readthedocs.io/en/latest/user/extensions.html#managing-plugins-with-plugin-manager).</p> <p><strong>Affected:</strong> Homebrew: jupyterlab</p> <p>JupyterLab&#39;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`.</p> <p>### Impact</p> <p>Users could workaround the plugin manager lock rules via direct API access for either: - child plugins of extensions covering multiple plugins - when &#34;lock all&#34; was issued by the administrator</p> <p>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.</p> <p>### Patches</p> <p>JupyterLab [`v4.6.2`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2) and [`v4.5.10`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10) contain the patch.</p> <p>Users of applications that depend on JupyterLab, such as Notebook v7+, should update `jupyterlab` package too.</p> <p>### Workarounds</p> <p>Manually lock all plugins that should be locked. The core plugin identifiers can be found in [the documentation](https://jupyterlab.readthedocs.io/en/latest/extension/extension_points.html#core-plugins) and identifiers for all installed extensions are listed in the [Plugin Manager](https://jupyterlab.readthedocs.io/en/latest/user/extensions.html#managing-plugins-with-plugin-manager).</p> https://vulnerability.circl.lu/vuln/brew-jupyterlab-ghsa-h5v5-8746-g7mm https://vulnerability.circl.lu/vuln/cve-2026-73627 <p><strong>Affected:</strong> jupyterlab</p> <p>JupyterLab (pip package &#39;jupyterlab&#39;) versions &gt;=4.1.0,&lt;=4.5.9 and &gt;=4.6.0,&lt;=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 &#39;lock all&#39; 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.</p> <p><strong>Affected:</strong> jupyterlab</p> <p>JupyterLab (pip package &#39;jupyterlab&#39;) versions &gt;=4.1.0,&lt;=4.5.9 and &gt;=4.6.0,&lt;=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 &#39;lock all&#39; 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.</p> https://vulnerability.circl.lu/vuln/cve-2026-73627