jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 4.5.0 until 4.5.10 and 4.6.2, in jupyterlab/extensions/manager.py and jupyterlab/extensions/pypi.py, JupyterLab's PyPI extension manager enforces blocked_extensions_uris by comparing requested install names to blocklist entries with custom normalization that is weaker than PyPI package-name canonicalization. An authenticated user can request a PyPI-equivalent spelling such as JupyterLab.Git for a blocklisted package such as jupyterlab-git, and JupyterLab accepts the install request even though pip resolves the variant to the same package. Security impact requires an allowlist or blocklist intended to restrict package installation, the PyPI Extension Manager, and kernels and terminals that are disabled or delegated to remote hosts. The bypass lets an authenticated user install a prohibited extension, defeat integrity restrictions, and affect availability without gaining new read access. This issue is fixed in versions 4.5.10 and 4.6.2.
CVE-2026-73416
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-58521 (ENISA EUVD) · GHSA-89vp-jrxv-24w8 (GitHub Security Advisories) · PYSEC-2026-3670 (OSV.dev)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.1
- EG Score
- 6.1MEDIUMmedium confidence
- EG Risk
- 28EG Risk 28/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity61% × 45%Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.7% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.7%
- EPSS %ILE
- 51st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 22, 2026
Last Modified
September 18, 2026
Advisory Details (10)
Auto-updated Aug 13, 2026PyPI extension blocklist package-name canonicalization bypass · Advisory · jupyterlab/jupyterlab · GitHub
https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-89vp-jrxv-24w8v4.7.0a1
Patch available: jupyterlab/jupyterlab v4.7.0a1 (pre-release)
https://github.com/jupyterlab/jupyterlab/releases/tag/v4.7.0a1v4.6.2
Patch available: jupyterlab/jupyterlab v4.6.2
https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2v4.5.10
Patch available: jupyterlab/jupyterlab v4.5.10
https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10Backport of security patches to `4.5.x` branch
Fix merged in jupyterlab/jupyterlab PR #19186 on 2026-07-21 — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/pull/19186Backport of security patches to `4.6.x` branch
Fix merged in jupyterlab/jupyterlab PR #19185 on 2026-07-21 — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/pull/19185Security patches
Fix merged in jupyterlab/jupyterlab PR #19184 on 2026-07-21 — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/pull/19184commit f1beab4a2027 (jupyterlab/jupyterlab)
Fix landed in jupyterlab/jupyterlab commit f1beab4a2027 — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/commit/f1beab4a2027af4719d6edc07d52d6cf5a39a432commit be9303f5bcd5 (jupyterlab/jupyterlab)
Fix landed in jupyterlab/jupyterlab commit be9303f5bcd5 — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/commit/be9303f5bcd5308eaeae953c5a3c903046682c2ccommit 9365f020baec (jupyterlab/jupyterlab)
Fix landed in jupyterlab/jupyterlab commit 9365f020baec — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/commit/9365f020baec5221deaf11535ed554c06637c999Vendor Advisories for CVE-2026-73416(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | jupyterlab @ 4.6.2 (fixes >= 4.6.0, <= 4.6.1) | — | ghsa |
| pip | jupyterlab @ 4.5.10 (fixes >= 4.5.0, <= 4.5.9) | — | ghsa |
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
(3 across 3 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| jupyterlab | 4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (29 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | 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) |
| — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| jupyterlab | 4.5.0 ... 4.6.1 (12 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 41× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 98 of 118 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 20 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-01 07:39 UTCGHSA enrichmentGHSA-89vp-jrxv-24w8 · GitHub severity MODERATE
- 2026-11-01 07:39 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-30 06:55 UTCOSV refresh
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-25 14:05 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-22 19:05 UTCEG score recompute
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-18 03:15 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 73 moreShow fewer
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-12 15:41 UTCEG score recompute
- 2026-10-11 19:26 UTCEG score recompute
- 2026-10-11 16:42 UTCEG score recompute
- 2026-10-11 14:01 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-10-04 12:45 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-10-03 03:30 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-10-01 06:25 UTCEG score recompute
- 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-28 05:14 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-23 22:25 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-09-22 23:00 UTCEG score recompute
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-09-20 01:58 UTCEG score recompute
- 2026-09-18 20:11 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-18 03:09 UTCEG score recompute
- 2026-09-17 04:36 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-16 06:55 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-14 16:43 UTCEG score recompute
- 2026-09-12 17:09 UTCEG score recompute
- 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-11 19:28 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-10 21:12 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-09 09:10 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-07 21:39 UTCEG score recompute
- 2026-09-06 17:28 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-05 19:32 UTCEG score recompute
- 2026-09-04 13:39 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-01 23:30 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-30 22:28 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-30 00:48 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-27 23:50 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-27 02:09 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-26 04:28 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-08-25 06:45 UTCEG score recompute
- 2026-08-23 11:24 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-22 13:44 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:jupyterlab
Frequently asked(5)
What is CVE-2026-73416?
When was the CVE record for CVE-2026-73416 published?
Is CVE-2026-73416 actively exploited?
What is the CVSS score of CVE-2026-73416?
How do I remediate CVE-2026-73416?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73416
Is Your Infrastructure Affected by CVE-2026-73416?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.