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. (CVE-2026-73627)
JupyterLab versions 4.1.0 through 4.5.9 and 4.6.0 through 4.6.1 contain a vulnerability that allows authenticated users to bypass plugin manager lock rules. This bypass occurs due to two server-side enforcement gaps, enabling users to enable or disable plugins that administrators have locked, including child plugins and those locked via the 'lock all' mechanism. This can undermine data integrity and bypass restrictions such as download or upload limits enforced through locked plugins. The issue is fixed in versions 4.5.10 and 4.6.2.
AI Analysis
Technical Summary
JupyterLab (pip package 'jupyterlab') versions >=4.1.0 <=4.5.9 and >=4.6.0 <=4.6.1 have a plugin manager lock-rule enforcement bypass vulnerability (CVE-2026-73627). Two server-side enforcement gaps allow authenticated users to circumvent administrator-imposed lock rules by making direct API requests to /lab/api/plugins, enabling or disabling locked plugins, including child plugins and those locked via the 'lock all' mechanism. This bypass can affect data integrity and bypass administrative restrictions implemented through locked plugins. The vulnerability is addressed in versions 4.5.10 and 4.6.2.
Potential Impact
Authenticated users can bypass administrative lock rules on plugins, potentially enabling or disabling plugins that should be locked. This can lead to compromised data integrity and circumvention of security or operational restrictions such as upload/download limits enforced by locked plugins. There is no indication of remote unauthenticated exploitation or privilege escalation beyond the authenticated user level.
Mitigation Recommendations
Upgrade affected JupyterLab installations to version 4.5.10 or later, or 4.6.2 or later, where the plugin manager lock-rule enforcement bypass is fixed. No other mitigation or temporary workaround is indicated in the available data.
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. (CVE-2026-73627)
Description
JupyterLab versions 4.1.0 through 4.5.9 and 4.6.0 through 4.6.1 contain a vulnerability that allows authenticated users to bypass plugin manager lock rules. This bypass occurs due to two server-side enforcement gaps, enabling users to enable or disable plugins that administrators have locked, including child plugins and those locked via the 'lock all' mechanism. This can undermine data integrity and bypass restrictions such as download or upload limits enforced through locked plugins. The issue is fixed in versions 4.5.10 and 4.6.2.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
JupyterLab (pip package 'jupyterlab') versions >=4.1.0 <=4.5.9 and >=4.6.0 <=4.6.1 have a plugin manager lock-rule enforcement bypass vulnerability (CVE-2026-73627). Two server-side enforcement gaps allow authenticated users to circumvent administrator-imposed lock rules by making direct API requests to /lab/api/plugins, enabling or disabling locked plugins, including child plugins and those locked via the 'lock all' mechanism. This bypass can affect data integrity and bypass administrative restrictions implemented through locked plugins. The vulnerability is addressed in versions 4.5.10 and 4.6.2.
Potential Impact
Authenticated users can bypass administrative lock rules on plugins, potentially enabling or disabling plugins that should be locked. This can lead to compromised data integrity and circumvention of security or operational restrictions such as upload/download limits enforced by locked plugins. There is no indication of remote unauthenticated exploitation or privilege escalation beyond the authenticated user level.
Mitigation Recommendations
Upgrade affected JupyterLab installations to version 4.5.10 or later, or 4.6.2 or later, where the plugin manager lock-rule enforcement bypass is fixed. No other mitigation or temporary workaround is indicated in the available data.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fpf6-h6p9-9rjr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-73627"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a7e0376bf8831d5398fa0d2
Added to database: 08/13/2026, 17:48:38 UTC
Last enriched: 08/13/2026, 18:14:46 UTC
Last updated: 09/27/2026, 13:47:47 UTC
Views: 43
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.