CVE-2026-102831

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.1Exploit: 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 JupyterLab 4.5.0 until 4.5.11 and 4.6.4, from Notebook 7.5.0 until 7.6.3, and from JupyterLite Core 0.7.0 until 0.8.4, the system clipboard cell-paste path accepts attacker-controlled cell JSON without clearing metadata.trusted. When useSystemClipboardForCells is active and pasteCodeCellsWithoutOutput is disabled, a pasted code cell can mark HTML output as trusted, bypass output sanitization, and execute script in the authenticated JupyterLab origin without executing the cell. Markdown and raw cells are not affected because their output is sanitized. This issue is fixed in JupyterLab 4.5.11 and 4.6.4, Notebook 7.6.3, and JupyterLite Core 0.8.4.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 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.2%
EPSS %ILE
8th
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

September 29, 2026

Last Modified

October 2, 2026

Advisory Details (6)

Auto-updated Sep 29, 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 cf6e89a8d315 (jupyterlab/jupyterlab)

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

https://github.com/jupyterlab/jupyterlab/commit/cf6e89a8d315c4134cefa50c220bca296da466a7
github_commit

commit 7f9f29e29e0c (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit 7f9f29e29e0c — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/7f9f29e29e0c83fb17b0f11da57d06b3c6a40d96
github_commit

commit 1a10a7da5ff6 (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit 1a10a7da5ff6 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/1a10a7da5ff655849b21581c2633b46483ae0be9
github Patch Available

Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboard · Advisory · jupyterlab/jupyterlab · GitHub

https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-6966-vjj6-99xv

Vendor Advisories for CVE-2026-102831(1)

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

Affected Packages

(4 across 1 ecosystem)
PyPI(4)
PackageVulnerable rangeFixed inDependents
jupyterlab4.6.0, 4.6.1, 4.6.2, 4.6.34.6.4—
jupyterlite0.7.0 ... 0.8.3 (17 versions)0.8.4—
jupyterlite-core0.7.0 ... 0.8.3 (17 versions)0.8.4—
notebook7.5.0 ... 7.6.2 (21 versions)7.6.3—

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-10-04 01:43 UTCEG score recompute
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-03 01:27 UTCEG score recompute
  4. 2026-10-02 13:18 UTCEG score recompute
  5. 2026-10-02 12:46 UTCEG score recompute
  6. 2026-10-01 20:00 UTCEG score recompute
  7. 2026-10-01 19:49 UTCEPSS rescore
  8. 2026-09-30 19:37 UTCEG score recompute
  9. 2026-09-30 15:02 UTCEPSS rescore
  10. 2026-09-29 19:20 UTCEG score recompute
  11. 2026-09-29 19:03 UTCEG score recompute
  12. 2026-09-29 19:03 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102831?
CVE-2026-102831 is a high vulnerability published on September 29, 2026. JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From JupyterLab 4.5.0 until 4.5.11 and 4.6.4, from Notebook 7.5.0 until 7.6.3, and from JupyterLite Core 0.7.0 until 0.8.4, the system clipboard cell-paste path accepts…
When was CVE-2026-102831 disclosed?
CVE-2026-102831 was first published on September 29, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102831 actively exploited?
CVE-2026-102831 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102831?
CVE-2026-102831 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102831?
A fix for CVE-2026-102831 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102831 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-102831

Explore →

Is Your Infrastructure Affected by CVE-2026-102831?

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

Book a Demo →Browse All CVEs