CVE-2026-73416

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
28(Track)
EG Risk 28/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 computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 22, 2026

Last Modified

August 17, 2026

Advisory Details (10)

Auto-updated Aug 13, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

PyPI extension blocklist package-name canonicalization bypass · Advisory · jupyterlab/jupyterlab · GitHub

https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-89vp-jrxv-24w8
github_release Patch Available

v4.7.0a1

Patch available: jupyterlab/jupyterlab v4.7.0a1 (pre-release)

https://github.com/jupyterlab/jupyterlab/releases/tag/v4.7.0a1
github_release Patch Available

v4.6.2

Patch available: jupyterlab/jupyterlab v4.6.2

https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2
github_release Patch Available

v4.5.10

Patch available: jupyterlab/jupyterlab v4.5.10

https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10
github_pr

Backport 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/19186
github_pr

Backport 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/19185
github_pr

Security patches

Fix merged in jupyterlab/jupyterlab PR #19184 on 2026-07-21 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/pull/19184
github_commit

commit f1beab4a2027 (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit f1beab4a2027 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/f1beab4a2027af4719d6edc07d52d6cf5a39a432
github_commit

commit be9303f5bcd5 (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit be9303f5bcd5 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/be9303f5bcd5308eaeae953c5a3c903046682c2c
github_commit

commit 9365f020baec (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit 9365f020baec — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/9365f020baec5221deaf11535ed554c06637c999

Vendor 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.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
jupyterlab4.6.0, 4.6.14.6.2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 26× 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.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 06:45 UTCEG score recompute
  3. 2026-08-23 11:24 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 13:44 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 16:03 UTCEG score recompute
  8. 2026-08-20 22:56 UTCEPSS rescore
  9. 2026-08-19 20:41 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 19:10 UTCEG score recompute
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-17 18:36 UTCEG score recompute
  15. 2026-08-17 17:30 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 15:27 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 17:47 UTCEG score recompute
  22. 2026-08-15 01:31 UTCEPSS rescore
  23. 2026-08-13 22:25 UTCEG score recompute
  24. 2026-08-13 22:09 UTCEG score recompute▲ 6.10
  25. 2026-08-13 22:09 UTCMITRE cvelistV5CVSS v3 → 6.1 · CVSS v4 → 6.1
Show 1 more
  1. 2026-08-12 20:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-73416?
CVE-2026-73416 is a medium vulnerability published on July 22, 2026. 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…
When was CVE-2026-73416 disclosed?
CVE-2026-73416 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73416 actively exploited?
CVE-2026-73416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.3% of all scored CVEs.
What is the CVSS score of CVE-2026-73416?
CVE-2026-73416 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-73416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73416, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73416

Explore →

Is Your Infrastructure Affected by CVE-2026-73416?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs