Authenticated plugin control via incomplete lock checks
Published Aug 13, 2026 · Updated Aug 13, 2026
Authorization bypass in JupyterLab 4.1.0 through 4.5.9 and 4.6.0 through 4.6.1 allows remote authenticated users to alter locked plugins. The PluginManager checks child plugins only against full identifiers and receives the global-lock setting under an unused option key. Direct requests to /lab/api/plugins can therefore enable or disable protected plugins when a parent extension or all plugins are locked, bypassing plugin-enforced data controls.
Summary
What happened
Authorization bypass in JupyterLab 4.1.0 through 4.5.9 and 4.6.0 through 4.6.1 allows remote authenticated users to alter locked plugins. The PluginManager checks child plugins only against full identifiers and receives the global-lock setting under an unused option key. Direct requests to /lab/api/plugins can therefore enable or disable protected plugins when a parent extension or all plugins are locked, bypassing plugin-enforced data controls.
The record
- CVE
- CVE-2026-73627
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Project Jupyter
- Product
- JupyterLab
- Classifications
- CWE-602, CWE-863, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo