jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. Prior to 4.5.10 and 4.6.2, in packages/imageviewer/src/widget.ts, JupyterLab's ImageViewer uses URL.createObjectURL for a specially crafted SVG image and revokes the blob URL too early, allowing the image to retain an executable same-origin context when it is opened through the image viewer and then opened in a new browser tab. The resulting cross-site scripting can be used to execute arbitrary code on the JupyterLab server. This issue is fixed in versions 4.5.10 and 4.6.2.
CVE-2026-73415
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 54% 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity75% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 46%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
September 9, 2026
Advisory Details (10)
Auto-updated Aug 12, 2026Image viewer in JupyterLab allows XSS when opening malicious image in new browser tab · Advisory · jupyterlab/jupyterlab · GitHub
https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-gx64-gj6p-pc4cv4.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-73415(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
(3 across 3 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 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jupyterlab | 0.0.1 ... 4.6.1 (589 versions) | 4.6.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 73× 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.
- 2026-09-19 00:33 UTCEG score recompute
- 2026-09-19 00:33 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 12:54 UTCVendor advisory
- 2026-09-18 00:31 UTCEG score recompute
- 2026-09-18 00:31 UTCVendor advisory
- 2026-09-17 12:15 UTCVendor advisory
- 2026-09-17 00:17 UTCEG score recompute
- 2026-09-17 00:17 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 10:49 UTCEG score recompute
- 2026-09-16 10:49 UTCVendor advisory
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 21:58 UTCVendor advisory
- 2026-09-15 09:28 UTCEG score recompute
- 2026-09-15 09:28 UTCVendor advisory
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 21:48 UTCVendor advisory
- 2026-09-14 06:41 UTCVendor advisory
- 2026-09-13 19:03 UTCEG score recompute
- 2026-09-13 19:03 UTCVendor advisory
- 2026-09-13 07:17 UTCVendor advisory
- 2026-09-12 19:39 UTCEG score recompute
- 2026-09-12 19:39 UTCVendor advisory
- 2026-09-12 15:02 UTCEPSS rescore
Show 69 moreShow fewer
- 2026-09-12 08:00 UTCVendor advisory
- 2026-09-11 20:21 UTCEG score recompute
- 2026-09-11 20:21 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 08:30 UTCVendor advisory
- 2026-09-10 20:52 UTCEG score recompute
- 2026-09-10 20:52 UTCVendor advisory
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 09:13 UTCVendor advisory
- 2026-09-09 21:28 UTCVendor advisory
- 2026-09-09 17:50 UTCVendor advisory
- 2026-09-09 05:11 UTCEG score recompute
- 2026-09-09 05:11 UTCVendor advisory
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:41 UTCEG score recompute
- 2026-09-06 23:59 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 00:33 UTCEG score recompute
- 2026-09-05 01:01 UTCEG score recompute
- 2026-09-04 13:12 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 23:26 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 23:16 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 11:38 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:51 UTCEG score recompute
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 08:13 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 08:32 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 00:51 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 01:19 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 14:23 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 15:04 UTCEG score recompute
- 2026-08-23 04:08 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 04:49 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 05:32 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 18:35 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 18:30 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 19:13 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 18:25 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:46 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 07:31 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 08:14 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 21:21 UTCEG score recompute
- 2026-08-12 21:01 UTCEG score recompute
- 2026-08-12 20:19 UTCEG score recompute
- 2026-08-12 20:06 UTCEG score recompute
- 2026-08-12 20:05 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-73415?
When was CVE-2026-73415 disclosed?
Is CVE-2026-73415 actively exploited?
What is the CVSS score of CVE-2026-73415?
How do I remediate CVE-2026-73415?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73415
Is Your Infrastructure Affected by CVE-2026-73415?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.