CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NHigh (8.1) in jupyterlab. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in jupyterlab 4.5.11, 4.6.4.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:Njupyterlab (PyPI): fixed in 4.6.4, 4.5.11notebook (PyPI): fixed in 7.6.3jupyterlite (PyPI): fixed in 0.8.4jupyterlite-core (PyPI): fixed in 0.8.4Explain CVE-2026-102831 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102831?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102831?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102831 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| jupyterlab | >= 4.5.0, < 4.5.11 |
| jupyterlab | >= 4.6.0, < 4.6.4 |
| jupyterlab notebook | >= 7.5.0, < 7.6.3 |
| jupyterlab jupyterlite-core | >= 0.7.0, < 0.8.4 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-6966-vjj6-99xv | PyPI | jupyterlab | >=4.6.0 <4.6.4 | 4.6.4 |
| GHSA-6966-vjj6-99xv | PyPI | jupyterlab | >=4.5.0 <4.5.11 | 4.5.11 |
| GHSA-6966-vjj6-99xv | PyPI | notebook | >=7.5.0 <7.6.3 | 7.6.3 |
| GHSA-6966-vjj6-99xv | PyPI | jupyterlite | >=0.7.0 <0.8.4 | 0.8.4 |
| GHSA-6966-vjj6-99xv | PyPI | jupyterlite-core | >=0.7.0 <0.8.4 | 0.8.4 |
| PYSEC-2026-4057 | PyPI | jupyterlab | >=4.5.0 <4.5.11 >=4.6.0 <4.6.4 | 4.5.11, 4.6.4 |
| PYSEC-2026-4058 | PyPI | jupyterlite | >=0.7.0 <0.8.4 | 0.8.4 |
| PYSEC-2026-4060 | PyPI | jupyterlite-core | >=0.7.0 <0.8.4 | 0.8.4 |
| PYSEC-2026-4112 | PyPI | notebook | >=7.5.0 <7.6.3 | 7.6.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | jupyter-notebook | no fix listed | DEBIAN-CVE-2026-102831 |
| Ubuntu | 18.04:LTS, 20.04:LTS, Pro:22.04:LTS and 1 more | jupyter-notebook | no fix listed | UBUNTU-CVE-2026-102831 |
| Ubuntu | 26.04:LTS, 26.10 | jupyterlab, jupyter-notebook | no fix listed | UBUNTU-CVE-2026-102831 |
| openSUSE | Tumbleweed | python-jupyterlab | 4.5.11-1.1 | openSUSE-SU-2026:11945-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Important.
An IMPORTANT severity cross-site scripting (XSS) flaw was found in JupyterLab, which Red Hat ships within Red Hat OpenShift AI (RHOAI) and Migration Toolkit for Applications offerings. When the useSystemClipboardForCells setting is enabled and pasteCodeCellsWithoutOutput is disabled (the default), the system clipboard cell-paste path accepts attacker-controlled cell JSON without clearing metadata.trusted. A pasted code cell can therefore mark its HTML output as trusted, bypass output sanitization, and execute attacker-supplied script in the authenticated JupyterLab origin as soon as the cell is pasted, without the user executing it. Running in the victim's session, the script can call the Jupyter Server REST API as that user, reading and writing any file under the server root, starting a kernel and running code in it, and opening a terminal where terminals are enabled. A remote attacker needs no JupyterLab account and no access to the server; exploitation requires enticing a user to copy malicious content and paste it into JupyterLab. Markdown and raw cells are not affected because their output is always sanitized. Red Hat's CVSS 3.1 score of 8.1 (IMPORTANT) matches the upstream score and reflects JupyterLab 4.5.0 and 4.5.1, where the system clipboard path is always active; from 4.5.2 the useSystemClipboardForCells setting is off by default, which lowers the practical attack complexity for deployments that keep that default. JupyterLab releases prior to 4.5.0, such as those bundled in some Red Hat OpenShift AI images, are not affected because the vulnerable system clipboard paste path was introduced in 4.5.0. This issue is delegated to the responsible Red Hat product teams and a fix is being pursued.
Upstream provides fixed releases (JupyterLab 4.5.11 and 4.6.4, Notebook 7.6.3, and JupyterLite Core 0.8.4), and upgrading to a release containing the fix is the recommended resolution. For deployments that cannot immediately upgrade, the upstream advisory documents the following workarounds:
On JupyterLab 4.5.2 and later, disable the system clipboard for cells (it is off by default on these versions). This can be confirmed under Settings, Notebook, or set in the raw settings:
{
"@jupyterlab/notebook-extension:tracker": {
"useSystemClipboardForCells": false
}
}
With this setting off, cell copy and paste use JupyterLab's in-application clipboard, which never leaves the page; the cost is that cells can no longer be copied between browser tabs or windows.
Alternatively, pasting cells without their outputs also stops the script from running, at the cost of discarding outputs on every paste:
{
"@jupyterlab/notebook-extension:tracker": {
"pasteCodeCellsWithoutOutput": true
}
}
On JupyterLab 4.5.0 and 4.5.1 there is no configuration opt-out, as every paste reads the system clipboard; upgrading is highly recommended for those versions.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift AI 2.25 | rhoai/odh-feature-server-rhel9:1792148523 | Fixed 2026-10-21 | RHSA-2026:87410 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-feature-server-rhel9:1791863220 | Fixed 2026-10-19 | RHSA-2026:84734 |
| Migration Toolkit for Applications 8 | mta/mta-solution-server-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cpu-torch210-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cpu-torch291-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cuda130-torch210-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cuda130-torch291-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-rocm64-torch291-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-cpu-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-cuda-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-rocm-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-minimal-rocm-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9 | Affected | |
| 2 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102831.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).