Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.20% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-102831High confidence
JupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboard
jupyterlab · jupyterlab
Official source article: GitHub GHSA-6966-VJJ6-99XV ↗. Check the applicable product and release in the original source.
8.1HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs jupyterlab jupyterlab and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 21 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 4 affected package states with no published fix
Distribution package intelligence
8 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | jupyter-notebook | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian trixietrixie · source | jupyterlab | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian bookwormbookworm · source | jupyter-notebook | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | jupyter-notebook | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | jupyterlab | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | jupyter-notebook | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | jupyterlab | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Ubuntu 24.04 LTSnoble · esm-apps | jupyter-notebook | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 7 Oct 2026 |
Open-source package ranges14 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| PyPIjupyterlab | ECOSYSTEM: introduced 4.6.0; fixed 4.6.4 | 4.6.4 | OSV record ↗aggregator derived · 1 Oct 2026 |
| PyPIjupyterlab | ECOSYSTEM: introduced 4.5.0; fixed 4.5.11 | 4.5.11 | OSV record ↗aggregator derived · 1 Oct 2026 |
| PyPIjupyterlab | ECOSYSTEM: introduced 4.5.0; fixed 4.5.11; introduced 4.6.0; fixed 4.6.4 | 4.5.11, 4.6.4 | OSV record ↗source linked ecosystem record · 1 Oct 2026 |
| PyPIjupyterlite | ECOSYSTEM: introduced 0.7.0; fixed 0.8.4 | 0.8.4 | OSV record ↗aggregator derived · 1 Oct 2026 |
| PyPIjupyterlite | ECOSYSTEM: introduced 0.7.0; fixed 0.8.4 | 0.8.4 | OSV record ↗source linked ecosystem record · 1 Oct 2026 |
| PyPIjupyterlite-core | ECOSYSTEM: introduced 0.7.0; fixed 0.8.4 | 0.8.4 | OSV record ↗aggregator derived · 1 Oct 2026 |
| PyPIjupyterlite-core | ECOSYSTEM: introduced 0.7.0; fixed 0.8.4 | 0.8.4 | OSV record ↗source linked ecosystem record · 1 Oct 2026 |
| PyPInotebook | ECOSYSTEM: introduced 7.5.0; fixed 7.6.3 | 7.6.3 | OSV record ↗aggregator derived · 1 Oct 2026 |
| PyPInotebook | ECOSYSTEM: introduced 7.5.0; fixed 7.6.3 | 7.6.3 | OSV record ↗source linked ecosystem record · 5 Oct 2026 |
| pipjupyterlab | >= 4.6.0, <= 4.6.3 | 4.6.4 | GitHub advisory ↗upstream repository advisory · 1 Oct 2026 |
| pipjupyterlab | >= 4.5.0, <= 4.5.10 | 4.5.11 | GitHub advisory ↗upstream repository advisory · 1 Oct 2026 |
| pipjupyterlite | >= 0.7.0, <= 0.8.3 | 0.8.4 | GitHub advisory ↗upstream repository advisory · 1 Oct 2026 |
| pipjupyterlite-core | >= 0.7.0, <= 0.8.3 | 0.8.4 | GitHub advisory ↗upstream repository advisory · 1 Oct 2026 |
| pipnotebook | >= 7.5.0, <= 7.6.2 | 7.6.3 | GitHub advisory ↗upstream repository advisory · 1 Oct 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-102831 · CSAF 2.0 · revision 3 · interimSUSE Product Security TeamCVE-2026-102831
The vendor recommends these product versions as the target state.
- jupyter-jupyterlab-4.5.11-1.1 as component of openSUSE Tumbleweed
- python313-jupyterlab-4.5.11-1.1 as component of openSUSE Tumbleweed
- python314-jupyterlab-4.5.11-1.1 as component of openSUSE Tumbleweed
- Summary
- 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.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-102831 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjupyterlab: JupyterLab: Cross-Site Scripting via malicious clipboard cell pasting
The vendor explicitly identifies these products as affected by this CVE.
- mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8
- rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th-torch-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th-torch-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th-torch-rocm-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th06-cpu-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th06-cuda130-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th06-cuda130-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-th06-rocm64-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
- Summary
- A flaw was found in JupyterLab. This vulnerability allows Cross-Site Scripting (XSS) when pasting notebook cells from the system clipboard, as the application fails to clear trusted metadata flags from imported cell data. A remote attacker could exploit this by enticing a user to paste malicious cell content, bypassing output sanitization. Successful exploitation enables the execution of arbitrary scripts within the user's authenticated session, potentially leading to unauthorized actions and information disclosure.
- Remediation
- Affected
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
Attacker-controlled content can reach a browser as executable script without sufficient output encoding or sanitisation.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
Attacker-controlled content can reach a browser as executable script without sufficient output encoding or sanitisation.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-79 ↗
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 29 Sept 2026 · Last source change 2 Oct 2026, 12:22 UTC · CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-30
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-89338
Product sourceCNA
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.SUSE Product Security Team ↗
- Before
- Awaiting fix
- After
- Mitigation available
- ENISA EUVD mappingEUVD-2026-89338 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-89338"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.