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.7% (49th percentile of EPSS-scored CVEs). 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.7%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100CISA SSVC

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%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 22, 2026

Last Modified

September 18, 2026

Advisory Details (10)

Auto-updated Aug 13, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
githubMentions a patch (unverified)

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

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jupyterlab4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (29 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jupyterlab4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (26 versions)
  • every version up to 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4: fixed in 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jupyterlab4.5.0 ... 4.6.1 (12 versions)
  • 4.6.0 up to 4.6.2: fixed in 4.6.2
  • 4.5.0 up to 4.5.10: fixed in 4.5.10
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 37× 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-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 12:45 UTCEG score recompute
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 03:30 UTCEG score recompute
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-10-01 06:25 UTCEG score recompute
  12. 2026-09-29 15:24 UTCEPSS rescore
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-28 05:14 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescore
  16. 2026-09-26 15:59 UTCEPSS rescore
  17. 2026-09-23 22:25 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-22 23:00 UTCEG score recompute
  20. 2026-09-21 21:09 UTCEPSS rescore
  21. 2026-09-20 20:16 UTCEPSS rescore
  22. 2026-09-20 01:58 UTCEG score recompute
  23. 2026-09-18 20:11 UTCEG score recompute
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-18 03:09 UTCEG score recompute
Show 62 more
  1. 2026-09-17 04:36 UTCEG score recompute
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 06:55 UTCEG score recompute
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-14 16:43 UTCEG score recompute
  7. 2026-09-12 17:09 UTCEG score recompute
  8. 2026-09-12 15:02 UTCEPSS rescore
  9. 2026-09-11 19:28 UTCEG score recompute
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-10 21:12 UTCEG score recompute
  12. 2026-09-10 09:35 UTCEPSS rescore
  13. 2026-09-09 09:10 UTCEG score recompute
  14. 2026-09-08 22:01 UTCEPSS rescore
  15. 2026-09-07 21:39 UTCEG score recompute
  16. 2026-09-06 17:28 UTCEG score recompute
  17. 2026-09-06 13:48 UTCEPSS rescore
  18. 2026-09-05 19:32 UTCEG score recompute
  19. 2026-09-04 13:39 UTCEG score recompute
  20. 2026-09-04 05:07 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 23:30 UTCEG score recompute
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-08-30 22:28 UTCEG score recompute
  27. 2026-08-30 19:18 UTCEPSS rescore
  28. 2026-08-30 19:17 UTCEPSS rescore
  29. 2026-08-30 01:22 UTCEPSS rescore
  30. 2026-08-30 00:48 UTCEG score recompute
  31. 2026-08-28 21:42 UTCEPSS rescore
  32. 2026-08-27 23:50 UTCEG score recompute
  33. 2026-08-27 14:25 UTCEPSS rescore
  34. 2026-08-27 02:09 UTCEG score recompute
  35. 2026-08-26 14:47 UTCEPSS rescore
  36. 2026-08-26 04:28 UTCEG score recompute
  37. 2026-08-25 13:49 UTCEPSS rescore
  38. 2026-08-25 06:45 UTCEG score recompute
  39. 2026-08-23 11:24 UTCEG score recompute
  40. 2026-08-23 00:19 UTCEPSS rescore
  41. 2026-08-22 13:44 UTCEG score recompute
  42. 2026-08-21 23:49 UTCEPSS rescore
  43. 2026-08-21 16:03 UTCEG score recompute
  44. 2026-08-20 22:56 UTCEPSS rescore
  45. 2026-08-19 20:41 UTCEG score recompute
  46. 2026-08-19 17:04 UTCEPSS rescore
  47. 2026-08-18 19:10 UTCEG score recompute
  48. 2026-08-18 13:49 UTCEPSS rescore
  49. 2026-08-18 13:49 UTCEPSS rescore
  50. 2026-08-17 18:36 UTCEG score recompute
  51. 2026-08-17 17:30 UTCEG score recompute
  52. 2026-08-17 13:47 UTCEPSS rescore
  53. 2026-08-16 15:27 UTCEG score recompute
  54. 2026-08-16 14:56 UTCEPSS rescore
  55. 2026-08-16 14:56 UTCEPSS rescore
  56. 2026-08-16 02:15 UTCEPSS rescore
  57. 2026-08-15 17:47 UTCEG score recompute
  58. 2026-08-15 01:31 UTCEPSS rescore
  59. 2026-08-13 22:25 UTCEG score recompute
  60. 2026-08-13 22:09 UTCEG score recompute▲ 6.10
  61. 2026-08-13 22:09 UTCMITRE cvelistV5CVSS v3 → 6.1 · CVSS v4 → 6.1
  62. 2026-08-12 20:21 UTCEG score recompute

Related CVEs(same product + same CWE)

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 on July 22, 2026, with the most recent update on September 18, 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.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73416?
CVE-2026-73416 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73416?
A fix for CVE-2026-73416 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73416 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs