CVE-2026-73415

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (55th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-57535 (ENISA EUVD) · GHSA-gx64-gj6p-pc4c (GitHub Security Advisories) · PYSEC-2026-3671 (OSV.dev)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • 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
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
55th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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.
GitHub advisoryMentions 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 pull request

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 pull request

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 pull request

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(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17925631272026-10-21redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17918295302026-10-19redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat
pipjupyterlab @ 4.6.2 (fixes >= 4.6.0, <= 4.6.1)—ghsa
pipjupyterlab @ 4.5.10 (fixes <= 4.5.9)—ghsa

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 9× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 205 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  3. 2026-11-12 08:33 UTCEchelonGraph re-scored
  4. 2026-11-12 08:33 UTCVendor advisory
  5. 2026-11-12 08:33 UTCGHSA enrichmentGHSA-gx64-gj6p-pc4c · GitHub severity HIGH
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  9. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  11. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  13. 2026-11-04 22:44 UTCEchelonGraph re-scored
  14. 2026-11-04 22:44 UTCVendor advisory
  15. 2026-11-04 22:44 UTCGHSA enrichmentGHSA-gx64-gj6p-pc4c · GitHub severity HIGH
  16. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  17. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  18. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  19. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  20. 2026-11-01 07:39 UTCGHSA enrichmentGHSA-gx64-gj6p-pc4c · GitHub severity HIGH
  21. 2026-11-01 07:39 UTCEchelonGraph re-scored
  22. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  23. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  24. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  25. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
Show 75 more
  1. 2026-10-28 12:34 UTCEchelonGraph re-scored
  2. 2026-10-28 12:34 UTCVendor advisory
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-10-25 14:05 UTCEchelonGraph re-scored
  7. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  9. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-10-20 18:36 UTCEchelonGraph re-scored
  12. 2026-10-20 18:36 UTCVendor advisory
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-18 03:15 UTCEchelonGraph re-scored
  16. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-10-13 07:54 UTCEchelonGraph re-scored
  22. 2026-10-13 07:54 UTCVendor advisory
  23. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-12 15:41 UTCEchelonGraph re-scored
  25. 2026-10-11 19:26 UTCEchelonGraph re-scored
  26. 2026-10-11 16:42 UTCEchelonGraph re-scored
  27. 2026-10-11 14:01 UTCEchelonGraph re-scored
  28. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  29. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  31. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  32. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  33. 2026-10-07 02:23 UTCEchelonGraph re-scored
  34. 2026-10-07 02:23 UTCVendor advisory
  35. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-10-06 14:09 UTCEchelonGraph re-scored
  37. 2026-10-06 14:09 UTCVendor advisory
  38. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  39. 2026-10-05 14:44 UTCEchelonGraph re-scored
  40. 2026-10-05 14:44 UTCVendor advisory
  41. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  42. 2026-10-04 22:27 UTCVendor advisory
  43. 2026-10-04 07:34 UTCVendor advisory
  44. 2026-10-03 19:56 UTCEchelonGraph re-scored
  45. 2026-10-03 19:56 UTCVendor advisory
  46. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  47. 2026-10-02 21:58 UTCEchelonGraph re-scored
  48. 2026-10-02 21:58 UTCVendor advisory
  49. 2026-10-02 08:18 UTCEchelonGraph re-scored
  50. 2026-10-02 08:18 UTCVendor advisory
  51. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  52. 2026-10-01 09:31 UTCVendor advisory
  53. 2026-09-30 21:53 UTCEchelonGraph re-scored
  54. 2026-09-30 21:53 UTCVendor advisory
  55. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  56. 2026-09-29 04:28 UTCEchelonGraph re-scored
  57. 2026-09-29 04:28 UTCVendor advisory
  58. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  59. 2026-09-28 12:54 UTCVendor advisory
  60. 2026-09-28 01:16 UTCEchelonGraph re-scored
  61. 2026-09-28 01:16 UTCVendor advisory
  62. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  63. 2026-09-27 09:52 UTCEchelonGraph re-scored
  64. 2026-09-27 09:52 UTCVendor advisory
  65. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  66. 2026-09-25 03:39 UTCEchelonGraph re-scored
  67. 2026-09-25 03:39 UTCVendor advisory
  68. 2026-09-24 11:11 UTCVendor advisory
  69. 2026-09-23 23:33 UTCEchelonGraph re-scored
  70. 2026-09-23 23:33 UTCVendor advisory
  71. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  72. 2026-09-23 11:29 UTCVendor advisory
  73. 2026-09-22 23:50 UTCEchelonGraph re-scored
  74. 2026-09-22 23:50 UTCVendor advisory
  75. 2026-09-22 11:56 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-73415?
CVE-2026-73415 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-73415 published?
The CVE record for CVE-2026-73415 was published on August 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
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 (55th 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.