JupyterLab Desktop: Cross-Site Scripting (XSS) leading to Remote Code Execution on Connect URL
JupyterLab Desktop versions before 4.6.2-1 are exposed on all platforms (macOS, Windows, Linux) when a user connects to an attacker-crafted remote server URL. The fix is in 4.6.2-1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.2-1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. JupyterLab Desktop versions prior to 4.6.2-1 A victim must be convinced to connect to an attacker-controlled or attacker-crafted remote server URL Affects all platforms (macOS, Windows, Linux)
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
JupyterLab Desktop, the cross-platform desktop app for JupyterLab, is affected by a cross-site scripting flaw in how it handles remote-server URLs in its server-selection dialog and Welcome view. Remotely, without logging in, an attacker can get a user to submit a crafted URL, then run JavaScript that abuses the app's privileged bridge to execute arbitrary code with that user's privileges.
Read the original description
JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, remote-server URLs were inserted into the server-selection dialog and Welcome view without safe encoding. An attacker who convinces a user to submit a crafted URL can execute JavaScript in the Welcome renderer and abuse its privileged IPC bridge to execute arbitrary code with the user’s privileges. The Welcome view also unsafely renders RSS news-feed titles; exploitation through this separate input path requires control over content delivered through the application’s Jupyter Blog feed or its cached feed data, rather than submission of a remote-server URL. This issue affects all supported platforms and is fixed in version 4.6.2-1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
JupyterLab Desktop versions prior to 4.6.2-1 A victim must be convinced to connect to an attacker-controlled or attacker-crafted remote server URL Affects all platforms (macOS, Windows, Linux)Upgrade to a fixed version: 4.6.2-1.
Workaround: Only connect to remote Jupyter servers whose URLs have been obtained from a trusted source.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- jupyterlab jupyterlab-desktop
fixed in 4.6.2-1
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-102530
Is CVE-2026-102530 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
JupyterLab Desktop placed user-supplied remote server URLs into its interface without sanitizing or encoding them. A crafted URL can therefore run malicious script inside the app, which can lead to full remote code execution with the privileges of the user running the application.Source: github.com
Which versions are affected by CVE-2026-102530?
jupyterlab-desktop: before 4.6.2-1.Source: cve.now feed data
Am I affected, and how do I check?
All JupyterLab Desktop versions prior to 4.6.2-1 are affected, on macOS, Windows, and Linux. To check, compare the installed JupyterLab Desktop version with 4.6.2-1.Source: github.com
How do I fix CVE-2026-102530?
Upgrade JupyterLab Desktop to 4.6.2-1, which all users should do. Until the upgrade is done, only connect to remote Jupyter servers whose URLs come from a trusted source.Source: github.com