---
title: "CVE-2026-102831: JupyterLab - Stored XSS"
description: "JupyterLab 4.5.0 to 4.5.11 and 4.6.4, Notebook 7.5.0 to 7.6.3, and JupyterLite Core 0.7.0 to 0.8.4 contain a stored XSS caused by improper clearing of metadata.trusted in clipboard cell-paste path, letting authenticated attackers execute scripts in the JupyterLab origin, exploit requires useSystemClipboardForCells enabled and pasteCodeCellsWithoutOutput disabled."
url: https://panop.io/threat-heartbeat/CVE-2026-102831/
---

# CVE-2026-102831 JupyterLab - Stored XSS

JupyterLab 4.5.0 to 4.5.11 and 4.6.4, Notebook 7.5.0 to 7.6.3, and JupyterLite Core 0.7.0 to 0.8.4 contain a stored XSS caused by improper clearing of metadata.trusted in clipboard cell-paste path, letting authenticated attackers execute scripts in the JupyterLab origin, exploit requires useSystemClipboardForCells enabled and pasteCodeCellsWithoutOutput disabled.

CVSS base score 8.1 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.20% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-102831)

## Details

Type

Stored XSS

Impact

Client Script Exec

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Published

29 September 2026

Updated

15 October 2026

Weakness

[CWE-79](https://cwe.mitre.org/data/definitions/79.html)

## Vendor fix

Update to JupyterLab 4.5.11 or 4.6.4, Notebook 7.6.3, and JupyterLite Core 0.8.4.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-102831](https://nvd.nist.gov/vuln/detail/CVE-2026-102831)
- [https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4)
- [https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-6966-vjj6-99xv](https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-6966-vjj6-99xv)
- [https://github.com/jupyterlab/jupyterlab/commit/1a10a7da5ff655849b21581c2633b46483ae0be9](https://github.com/jupyterlab/jupyterlab/commit/1a10a7da5ff655849b21581c2633b46483ae0be9)
- [https://github.com/jupyterlab/jupyterlab/commit/7f9f29e29e0c83fb17b0f11da57d06b3c6a40d96](https://github.com/jupyterlab/jupyterlab/commit/7f9f29e29e0c83fb17b0f11da57d06b3c6a40d96)
- [https://github.com/jupyterlab/jupyterlab/commit/cf6e89a8d315c4134cefa50c220bca296da466a7](https://github.com/jupyterlab/jupyterlab/commit/cf6e89a8d315c4134cefa50c220bca296da466a7)
- [https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)