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. 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 'lock all' 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.
CVE-2026-73627
This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.0
- EG Score
- 6.0(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity60% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
September 9, 2026
Advisory Details (2)
Auto-updated Aug 13, 2026JupyterLab 4.6.0 Plugin Manager Lock-Rule Enforcement Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/jupyterlab-plugin-manager-lock-rule-enforcement-bypassJupyterLab PluginManager lock-rule enforcement bypass · Advisory · jupyterlab/jupyterlab · GitHub
https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-h5v5-8746-g7mmVendor Advisories for CVE-2026-73627(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:1788185899 | 2026-09-08 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 2 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jupyterlab | 4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (27 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jupyterlab | 4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (26 versions) | 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 92× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 119 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 10:53 UTCEG score recompute
- 2026-09-18 10:53 UTCVendor advisory
- 2026-09-18 10:53 UTCGHSA enrichment
- 2026-09-17 12:09 UTCEG score recompute
- 2026-09-17 12:09 UTCVendor advisory
- 2026-09-17 12:09 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 12:07 UTCEG score recompute
- 2026-09-16 12:07 UTCVendor advisory
- 2026-09-16 12:07 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 13:22 UTCEG score recompute
- 2026-09-15 13:22 UTCVendor advisory
- 2026-09-15 13:22 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 14:38 UTCEG score recompute
- 2026-09-14 14:38 UTCVendor advisory
- 2026-09-14 14:38 UTCGHSA enrichment
- 2026-09-13 15:50 UTCVendor advisory
- 2026-09-13 15:50 UTCGHSA enrichment
- 2026-09-12 17:06 UTCEG score recompute
- 2026-09-12 17:06 UTCVendor advisory
- 2026-09-12 17:06 UTCGHSA enrichment
- 2026-09-12 15:02 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-11 18:21 UTCEG score recompute
- 2026-09-11 18:21 UTCVendor advisory
- 2026-09-11 18:21 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 19:36 UTCEG score recompute
- 2026-09-10 19:36 UTCVendor advisory
- 2026-09-10 19:36 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 20:51 UTCVendor advisory
- 2026-09-09 20:51 UTCGHSA enrichment
- 2026-09-09 05:06 UTCEG score recompute
- 2026-09-09 05:06 UTCVendor advisory
- 2026-09-09 05:06 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 22:15 UTCEG score recompute
- 2026-09-07 22:15 UTCGHSA enrichment
- 2026-09-06 23:28 UTCEG score recompute
- 2026-09-06 23:28 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 00:44 UTCEG score recompute
- 2026-09-06 00:44 UTCGHSA enrichment
- 2026-09-05 02:00 UTCEG score recompute
- 2026-09-05 02:00 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-04 03:15 UTCGHSA enrichment
- 2026-09-03 03:59 UTCEG score recompute
- 2026-09-03 03:59 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 05:14 UTCEG score recompute
- 2026-09-02 05:14 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 06:18 UTCEG score recompute
- 2026-09-01 06:18 UTCGHSA enrichment
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 07:32 UTCEG score recompute
- 2026-08-31 07:31 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 08:24 UTCEG score recompute
- 2026-08-30 08:24 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 09:39 UTCEG score recompute
- 2026-08-29 09:38 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 10:51 UTCEG score recompute
- 2026-08-28 10:51 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 12:04 UTCEG score recompute
- 2026-08-27 12:04 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 13:19 UTCGHSA enrichment
- 2026-08-25 14:30 UTCEG score recompute
- 2026-08-25 14:30 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 15:45 UTCEG score recompute
- 2026-08-24 15:45 UTCGHSA enrichment
- 2026-08-23 17:01 UTCEG score recompute
- 2026-08-23 17:01 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 18:17 UTCEG score recompute
- 2026-08-22 18:17 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 19:33 UTCEG score recompute
- 2026-08-21 19:33 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 20:49 UTCGHSA enrichment
- 2026-08-19 22:04 UTCEG score recompute
- 2026-08-19 22:03 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 23:19 UTCEG score recompute
- 2026-08-18 23:19 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 00:35 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-73627?
When was CVE-2026-73627 disclosed?
Is CVE-2026-73627 actively exploited?
What is the CVSS score of CVE-2026-73627?
How do I remediate CVE-2026-73627?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73627
Is Your Infrastructure Affected by CVE-2026-73627?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.