CVE-2026-86044
9.6 CRITICALpublic exploit availablePublished 2026-11-06 · Updated 2026-11-10
AI risk analysis
- Summary
- JupyterLab Desktop prior to 4.6.2-1 exposed the getServerInfo API to renderers without verifying the origin of the current page, allowing an attacker to exploit a MathJax link in an untrusted notebook to redirect the renderer while retaining access to the preload bridge, then retrieve server credentials and execute arbitrary code via the Jupyter REST API.
- Exploitability
- Exploitation requires user interaction (clicking a malicious link in a notebook) and relies on a specific chain involving outdated MathJax handling in versions before 4.4.8; users on 4.4.8+ are protected from the first step.
- Blast radius
- Successful exploitation grants full remote code execution as the victim user, enabling data theft, lateral movement, or persistence within the local Jupyter environment.
- Detection
- No reliable host or network indicator is derivable from the published description.
- Prioritized remediation
- Upgrade to JupyterLab Desktop version 4.6.2-1 or later.
Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.
NVD description
JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, JupyterLab Desktop exposed getServerInfo to the renderer without confirming that the current page still had the local Jupyter server origin. In a local managed session using JupyterLab before 4.4.8, an attacker can place a crafted MathJax link in an untrusted notebook. If a victim opens the notebook and clicks the link, the existing renderer navigates to an attacker-controlled site while retaining access to the preload bridge. The site can call getServerInfo to obtain the local server URL and authentication token, then use the Jupyter REST API to create and trust a notebook that executes arbitrary code as the victim. Users whose environment already uses JupyterLab 4.4.8 or later are unaffected because the corrected link handling breaks the first step of the chain. This vulnerability is fixed in 4.6.2-1.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Weaknesses
CWE-601
Public exploit & PoC references
- https://github.com/jupyterlab/jupyterlab-desktop/commit/7f8f64ae796efae77d106612c95f0edd6c5dc273
- https://github.com/jupyterlab/jupyterlab-desktop/releases/tag/v4.6.2-1
- https://github.com/jupyterlab/jupyterlab-desktop/security/advisories/GHSA-2mr8-962v-wc67
- https://github.com/jupyterlab/jupyterlab-desktop/security/advisories/GHSA-2mr8-962v-wc67
All references
- https://github.com/jupyterlab/jupyterlab-desktop/commit/7f8f64ae796efae77d106612c95f0edd6c5dc273
- https://github.com/jupyterlab/jupyterlab-desktop/releases/tag/v4.6.2-1
- https://github.com/jupyterlab/jupyterlab-desktop/security/advisories/GHSA-2mr8-962v-wc67
- https://github.com/jupyterlab/jupyterlab-desktop/security/advisories/GHSA-2mr8-962v-wc67
Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.
Related CVEs
- HIGHCVE-2014-125138PoC
- CRITICALCVE-2020-37282PoC
- HIGHCVE-2022-51019PoC
- CRITICALCVE-2023-54399
- CRITICALCVE-2023-54400PoC
- CRITICALCVE-2023-54405PoC
- CRITICALCVE-2024-31026
- CRITICALCVE-2024-4457PoC
Related by shared AI tags and CWE weakness class. Browse the full archive.