CVE-2026-73417

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd 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
8.6EG
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: 8.6Exploit: 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 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user's access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
39
EG Risk 39/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
Severity86% × 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

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)

Cross-site scripting (XSS) in JupyterLab via crafted settings file (`overrides.json`) · Advisory · jupyterlab/jupyterlab · GitHub

https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-pppj-hq3g-57pj
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-73417(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73417?
CVE-2026-73417 is a high vulnerability published on July 22, 2026. jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings…
When was CVE-2026-73417 disclosed?
CVE-2026-73417 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-73417 actively exploited?
CVE-2026-73417 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-73417?
CVE-2026-73417 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73417?
A fix for CVE-2026-73417 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73417 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-73417

Explore →

Is Your Infrastructure Affected by CVE-2026-73417?

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

Book a Demo →Browse All CVEs