CVE-2026-102832

MEDIUMPre-NVD 4.24.2
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
4.2EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.2Exploit: 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 4.5.7 until 4.5.11 and 4.6.4, the markdownviewer:trust and notebook:trust command-link handlers use tracker.currentWidget to resolve the current Markdown viewer or notebook when the user answers rather than retaining the document whose command button was clicked. If another document becomes current while the prompt is open and the user chooses Trust, JupyterLab marks the second document trusted while leaving the clicked document untrusted. Later command buttons in the incorrectly trusted document run without a prompt, and trusting a notebook marks all cells trusted, saves unsaved edits, and persists the server signature to disk. Applications that bundle JupyterLab, including affected Notebook and JupyterLite releases, inherit the behavior. This issue is fixed in versions 4.5.11 and 4.6.4.

CVSS v3
4.2
EG Score
4.2MEDIUMlow confidence
EG Risk
19
EG Risk 19/100

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 (value × EchelonGraph’s weight)
Severity42% × 45%
The EG Score, 4.2 of 10.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
—
EPSS %ILE
—
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

October 13, 2026

Last Modified

October 13, 2026

Advisory Details (6)

Auto-updated Oct 13, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v4.6.4

Patch available: jupyterlab/jupyterlab v4.6.4

https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4
GitHub release Patch Available

v4.5.11

Patch available: jupyterlab/jupyterlab v4.5.11

https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11
GitHub commit

commit f7e5f9803fdf (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit f7e5f9803fdf — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/f7e5f9803fdf2aaaa0e9bfb9cc73386a8cc5f0b2
GitHub commit

commit b64bc88b8ca0 (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit b64bc88b8ca0 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/b64bc88b8ca034cf158604a5cc48ca9170ea453b
GitHub commit

commit 0fc18ab4ef67 (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit 0fc18ab4ef67 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/0fc18ab4ef67e431a8f6560e387193baf786c70a
GitHub advisoryMentions a patch (unverified)

Command link trust prompt in JupyterLab can trust a document other than the one clicked · Advisory · jupyterlab/jupyterlab · GitHub

Affected: 4.5.7 and 4.6.0

https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-jwrc-gm9j-263p

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 4× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-10-13 17:29 UTCEG score recompute
  2. 2026-10-13 16:24 UTCEG score recompute
  3. 2026-10-13 15:40 UTCEG score recomputeFirst assessed: 4.2 MEDIUM
  4. 2026-10-13 15:39 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-102832?
CVE-2026-102832 is a medium-severity vulnerability; its CVE record was published on October 13, 2026. JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 4.5.7 until 4.5.11 and 4.6.4, the markdownviewer:trust and notebook:trust command-link handlers use tracker.currentWidget to resolve the current Markdown viewer or…
When was the CVE record for CVE-2026-102832 published?
The CVE record for CVE-2026-102832 was published on October 13, 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 October 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-102832?
CVE-2026-102832 has a CVSS base score of 4.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-102832?
A fix for CVE-2026-102832 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-102832

Explore →

Is Your Infrastructure Affected by CVE-2026-102832?

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