JupyterLab Desktop for macOS shipped before version 4.6.2-1 with Electron's RunAsNode fuse enabled, allowing the environment variable ELECTRON_RUN_AS_NODE to execute arbitrary Node.js code in the application process. An attacker who can already run arbitrary code as the user can therefore run code in JupyterLab Desktop's context and inherit any TCC permissions that the application already holds, such as access to Documents, Desktop or Downloads folders, without triggering a macOS prompt. This grants the attacker read or modify access to user files that would otherwise be protected, but does not provide initial or remote code execution.

The vulnerability impacts JupyterLab Desktop for macOS versions prior to 4.6.2-1. The affected product is JupyterLab Desktop, vendor JupyterLab. Only macOS installations are affected; Windows and Linux are not impacted.

The CVSS score of 5.5 indicates moderate severity. The EPSS score is not available, and the vulnerability is not listed in CISA KEV. Exploitation requires the attacker to already be able to execute code locally and for the application to have pre‑granted TCC permissions. The attack vector is therefore local and limited to environments where the user has already granted TCC permissions, making the risk lower than a generic remote code execution but still significant for exposed systems.