JupyterLab PluginManager lock-rule enforcement bypass
JupyterLab's plugin manager has a vulnerability that allows authenticated users to bypass administrator-imposed plugin lock rules via direct API requests. This bypass affects child plugins of multi-plugin extensions and scenarios where administrators issued a 'lock all' command. The flaw can undermine data integrity and circumvent restrictions implemented through locked plugins. Patches addressing this issue are available in JupyterLab versions 4.6.2 and 4.5.10. Users of dependent applications like Notebook v7+ should also update the jupyterlab package. As a workaround, administrators can manually lock all plugins that require restriction using documented plugin identifiers.
AI Analysis
Technical Summary
The vulnerability in JupyterLab's plugin manager arises from two server-side enforcement gaps that permit authenticated users to bypass plugin lock rules by sending direct requests to the /lab/api/plugins endpoint. This bypass enables users to override restrictions intended to prevent enabling or disabling certain plugins, including child plugins of extensions with multiple plugins and when a 'lock all' command is applied. The issue compromises the integrity of data and allows circumvention of user action restrictions enforced via locked plugins. Official patches were released in JupyterLab versions 4.6.2 and 4.5.10. Users of applications depending on JupyterLab, such as Notebook v7+, are advised to update accordingly. Manual plugin locking serves as a temporary mitigation.
Potential Impact
Authenticated users can bypass administrative controls designed to lock plugins, potentially affecting data integrity and allowing circumvention of restrictions such as download/upload limits enforced through locked plugins. This undermines the security hardening intended by plugin lock rules within single-user JupyterLab servers.
Mitigation Recommendations
Apply the official patches by upgrading to JupyterLab version 4.6.2 or 4.5.10 or later. Users of dependent applications like Notebook v7+ should also update the jupyterlab package. As a temporary workaround, manually lock all plugins that require restriction using the documented core plugin identifiers and those listed in the Plugin Manager. No indication exists that the vendor considers this issue mitigated without patching.
JupyterLab PluginManager lock-rule enforcement bypass
Description
JupyterLab's plugin manager has a vulnerability that allows authenticated users to bypass administrator-imposed plugin lock rules via direct API requests. This bypass affects child plugins of multi-plugin extensions and scenarios where administrators issued a 'lock all' command. The flaw can undermine data integrity and circumvent restrictions implemented through locked plugins. Patches addressing this issue are available in JupyterLab versions 4.6.2 and 4.5.10. Users of dependent applications like Notebook v7+ should also update the jupyterlab package. As a workaround, administrators can manually lock all plugins that require restriction using documented plugin identifiers.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in JupyterLab's plugin manager arises from two server-side enforcement gaps that permit authenticated users to bypass plugin lock rules by sending direct requests to the /lab/api/plugins endpoint. This bypass enables users to override restrictions intended to prevent enabling or disabling certain plugins, including child plugins of extensions with multiple plugins and when a 'lock all' command is applied. The issue compromises the integrity of data and allows circumvention of user action restrictions enforced via locked plugins. Official patches were released in JupyterLab versions 4.6.2 and 4.5.10. Users of applications depending on JupyterLab, such as Notebook v7+, are advised to update accordingly. Manual plugin locking serves as a temporary mitigation.
Potential Impact
Authenticated users can bypass administrative controls designed to lock plugins, potentially affecting data integrity and allowing circumvention of restrictions such as download/upload limits enforced through locked plugins. This undermines the security hardening intended by plugin lock rules within single-user JupyterLab servers.
Mitigation Recommendations
Apply the official patches by upgrading to JupyterLab version 4.6.2 or 4.5.10 or later. Users of dependent applications like Notebook v7+ should also update the jupyterlab package. As a temporary workaround, manually lock all plugins that require restriction using the documented core plugin identifiers and those listed in the Plugin Manager. No indication exists that the vendor considers this issue mitigated without patching.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-h5v5-8746-g7mm
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a616bcd9c2644c7f80dbd6b
Added to database: 07/23/2026, 01:18:05 UTC
Last enriched: 07/23/2026, 01:24:01 UTC
Last updated: 07/23/2026, 01:24:01 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.