CVE-2026-73415

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (52nd 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
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: 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. 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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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

August 12, 2026

Last Modified

September 9, 2026

Advisory Details (10)

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

Image 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-pc4c
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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat

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)
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
jupyterlab0.0.1 ... 4.6.1 (589 versions)
  • 4.6.0 up to 4.6.2: fixed in 4.6.2
  • every version up to 4.5.10: fixed in 4.5.10
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 151 total refreshes for this CVE.

  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-07 02:23 UTCEG score recompute
  5. 2026-10-07 02:23 UTCVendor advisory
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-06 14:09 UTCEG score recompute
  8. 2026-10-06 14:09 UTCVendor advisory
  9. 2026-10-05 17:43 UTCEPSS rescore
  10. 2026-10-05 14:44 UTCEG score recompute
  11. 2026-10-05 14:44 UTCVendor advisory
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-04 22:27 UTCVendor advisory
  14. 2026-10-04 07:34 UTCVendor advisory
  15. 2026-10-03 19:56 UTCEG score recompute
  16. 2026-10-03 19:56 UTCVendor advisory
  17. 2026-10-03 14:26 UTCEPSS rescore
  18. 2026-10-02 21:58 UTCEG score recompute
  19. 2026-10-02 21:58 UTCVendor advisory
  20. 2026-10-02 08:18 UTCEG score recompute
  21. 2026-10-02 08:18 UTCVendor advisory
  22. 2026-10-01 19:50 UTCEPSS rescore
  23. 2026-10-01 09:31 UTCVendor advisory
  24. 2026-09-30 21:53 UTCEG score recompute
  25. 2026-09-30 21:53 UTCVendor advisory
Show 75 more
  1. 2026-09-29 15:24 UTCEPSS rescore
  2. 2026-09-29 04:28 UTCEG score recompute
  3. 2026-09-29 04:28 UTCVendor advisory
  4. 2026-09-28 13:52 UTCEPSS rescore
  5. 2026-09-28 12:54 UTCVendor advisory
  6. 2026-09-28 01:16 UTCEG score recompute
  7. 2026-09-28 01:16 UTCVendor advisory
  8. 2026-09-27 13:48 UTCEPSS rescore
  9. 2026-09-27 09:52 UTCEG score recompute
  10. 2026-09-27 09:52 UTCVendor advisory
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-25 03:39 UTCEG score recompute
  13. 2026-09-25 03:39 UTCVendor advisory
  14. 2026-09-24 11:11 UTCVendor advisory
  15. 2026-09-23 23:33 UTCEG score recompute
  16. 2026-09-23 23:33 UTCVendor advisory
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 11:29 UTCVendor advisory
  19. 2026-09-22 23:50 UTCEG score recompute
  20. 2026-09-22 23:50 UTCVendor advisory
  21. 2026-09-22 11:56 UTCVendor advisory
  22. 2026-09-22 00:17 UTCEG score recompute
  23. 2026-09-22 00:17 UTCVendor advisory
  24. 2026-09-21 21:09 UTCEPSS rescore
  25. 2026-09-21 12:15 UTCVendor advisory
  26. 2026-09-21 00:31 UTCEG score recompute
  27. 2026-09-21 00:31 UTCVendor advisory
  28. 2026-09-20 20:16 UTCEPSS rescore
  29. 2026-09-20 12:46 UTCVendor advisory
  30. 2026-09-19 23:51 UTCEG score recompute
  31. 2026-09-19 23:51 UTCVendor advisory
  32. 2026-09-19 12:13 UTCVendor advisory
  33. 2026-09-19 00:33 UTCEG score recompute
  34. 2026-09-19 00:33 UTCVendor advisory
  35. 2026-09-18 19:28 UTCEPSS rescore
  36. 2026-09-18 12:54 UTCVendor advisory
  37. 2026-09-18 00:31 UTCEG score recompute
  38. 2026-09-18 00:31 UTCVendor advisory
  39. 2026-09-17 12:15 UTCVendor advisory
  40. 2026-09-17 00:17 UTCEG score recompute
  41. 2026-09-17 00:17 UTCVendor advisory
  42. 2026-09-16 14:08 UTCEPSS rescore
  43. 2026-09-16 10:49 UTCEG score recompute
  44. 2026-09-16 10:49 UTCVendor advisory
  45. 2026-09-16 05:15 UTCEPSS rescore
  46. 2026-09-15 21:58 UTCVendor advisory
  47. 2026-09-15 09:28 UTCEG score recompute
  48. 2026-09-15 09:28 UTCVendor advisory
  49. 2026-09-15 03:12 UTCEPSS rescore
  50. 2026-09-14 21:48 UTCVendor advisory
  51. 2026-09-14 06:41 UTCVendor advisory
  52. 2026-09-13 19:03 UTCEG score recompute
  53. 2026-09-13 19:03 UTCVendor advisory
  54. 2026-09-13 07:17 UTCVendor advisory
  55. 2026-09-12 19:39 UTCEG score recompute
  56. 2026-09-12 19:39 UTCVendor advisory
  57. 2026-09-12 15:02 UTCEPSS rescore
  58. 2026-09-12 08:00 UTCVendor advisory
  59. 2026-09-11 20:21 UTCEG score recompute
  60. 2026-09-11 20:21 UTCVendor advisory
  61. 2026-09-11 14:53 UTCEPSS rescore
  62. 2026-09-11 08:30 UTCVendor advisory
  63. 2026-09-10 20:52 UTCEG score recompute
  64. 2026-09-10 20:52 UTCVendor advisory
  65. 2026-09-10 09:35 UTCEPSS rescore
  66. 2026-09-10 09:13 UTCVendor advisory
  67. 2026-09-09 21:28 UTCVendor advisory
  68. 2026-09-09 17:50 UTCVendor advisory
  69. 2026-09-09 05:11 UTCEG score recompute
  70. 2026-09-09 05:11 UTCVendor advisory
  71. 2026-09-08 22:01 UTCEPSS rescore
  72. 2026-09-07 16:41 UTCEG score recompute
  73. 2026-09-06 23:59 UTCEG score recompute
  74. 2026-09-06 13:48 UTCEPSS rescore
  75. 2026-09-06 00:33 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-73415?
CVE-2026-73415 is a high vulnerability published on August 12, 2026. 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…
When was CVE-2026-73415 disclosed?
CVE-2026-73415 was first published on August 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73415 actively exploited?
CVE-2026-73415 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73415?
CVE-2026-73415 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73415?
A fix for CVE-2026-73415 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73415 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-73415

Explore →

Is Your Infrastructure Affected by CVE-2026-73415?

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