CVE-2025-55002: medium-severity vulnerability in jupyterlab-desktop
JupyterLab Desktop: TCC Bypass via Misconfigured Node Fuses
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.5epss 0.2%
JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, JupyterLab Desktop for macOS shipped with Electron's RunAsNode fuse enabled, allowing ELECTRON_RUN_AS_NODE to execute arbitrary Node.js code in the application process. An attacker who can already execute code as the current user can therefore run code in JupyterLab Desktop's context and inherit TCC permissions previously granted to the application, including access to protected Documents, Desktop, or Downloads folders without another macOS prompt. Exploitation requires existing local code execution and prior TCC grants; it does not provide initial or remote code execution. Windows and Linux are not affected. This vulnerability is fixed in 4.6.2-1.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected products
jupyterlab · jupyterlab-desktopRelated CVEs — jupyterlab-desktop
In the same product, most dangerous first.
CVE-2026-102530CRITICALJupyterLab Desktop: Cross-Site Scripting (XSS) leading to Remote Code Execution on Connect URLEPSS 0.4%CVE-2026-86044CRITICALJupyterLab Desktop: One-Click Jupyter Server Token Leak leading to Remote Code ExecutionEPSS 0.3%CVE-2025-54991MEDIUMJupyterLab Desktop: TCC Bypass via Insecure Entitlements (macOS)EPSS 0.2%