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 55% 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
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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
- 45%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
August 12, 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(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jupyterlab | 4.6.0, 4.6.1 | 4.6.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 30× 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-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
Show 5 moreShow fewer
- 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 CWE)
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.