Quick answers
- Is CVE-2026-102530 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102530 being exploited in the wild.
- How severe is CVE-2026-102530?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- JupyterLab Desktop prior to 4.6.2-1.
- Is there a fix for CVE-2026-102530?
- Yes: fixed in 4.6.2-1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102530 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102530?
- Check whether you run JupyterLab Desktop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.6.2-1
Technical details
The vulnerability is an unsafe innerHTML insertion (XSS) affecting two code paths: remote-server URLs concatenated directly into the DOM in the server-selection dialog and Welcome view, and RSS news-feed titles rendered without encoding. An attacker can exploit the first path by convincing a user to paste a crafted URL, or the second by compromising feed content or cached feed data. The privileged IPC bridge allows JavaScript executed in the Welcome renderer to escape the renderer process and execute arbitrary code with user privileges.
Affected products
- JupyterLab Desktop prior to 4.6.2-1
Timeline
- 2026-11-06: disclosed