CVE-2026-73627: jupyterlab · Client-Side Enforcement of Server-Side Security
Affects jupyterlabSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 4.6.2 when convenient.
Data as of 20 Nov 2026, 14:50 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.0 |
|---|
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-08-15.
- Patch
- Available – fixed in 4.6.2, 4.5.10
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade jupyterlab to 4.6.2; jupyterlab to 4.5.10; jupyterlab to 4.6.2 or 4.5.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jupyterlabjupyterlab | Affected
| Fixed in
|
| jupyterlabjupyterlab | Affected
| Fixed in
|
PyPIjupyterlabpkg:pypi/jupyterlabOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade JupyterLab to version 4.5.10 or later, or 4.6.2 or later, where this vulnerability is fixed. No other mitigation is indicated as the issue is resolved in these official releases.
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 server-side plugin lock rules by making direct API requests. This enables enabling or disabling plugins that administrators intended to lock, potentially affecting data integrity and bypassing security restrictions. The issue is fixed in versions 4.5.10 and 4.6.2.