Is CVE-2025-55002 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-55002 being exploited in the wild.

How severe is CVE-2025-55002?

Medium severity, with a CVSS score of 5.5, published 6 November 2026.

Which products and versions are affected?

Project Jupyter JupyterLab Desktop prior to 4.6.2-1 (macOS only).

How is CVE-2025-55002 attacked?

It is attacked with local access.

Am I affected by CVE-2025-55002?

Check whether you run Project Jupyter 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.

CVE-2025-55002: JupyterLab Desktop Electron fuse bypass on macOS

CVE-2025-55002 · Severity: medium · CVSS 5.5 · Published 2026-11-06

JupyterLab Desktop is a cross-platform IDE for data science and interactive computing. On macOS, versions prior to 4.6.2-1 shipped with Electron's RunAsNode fuse enabled, allowing an attacker with local code execution to bypass privacy controls (TCC permissions) that normally protect sensitive user folders. The vulnerability does not provide initial code execution; an attacker must already run code as the current user.

Vendors: Project Jupyter.

Quick answers

Is CVE-2025-55002 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-55002 being exploited in the wild.
How severe is CVE-2025-55002?: Medium severity, with a CVSS score of 5.5, published 6 November 2026.
Which products and versions are affected?: Project Jupyter JupyterLab Desktop prior to 4.6.2-1 (macOS only).
Is there a fix for CVE-2025-55002?: Yes: fixed in 4.6.2-1. Until then: Disable the RunAsNode Electron fuse and related environment variable features using electron-builder's afterPack hook with the @electron/fuses library to flip RunAsNode, EnableNodeOptionsEnvironmentVariable, and EnableNodeCliInspectArguments fuses to false. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-55002 attacked?: It is attacked with local access.
Am I affected by CVE-2025-55002?: Check whether you run Project Jupyter 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

Disable the RunAsNode Electron fuse and related environment variable features using electron-builder's afterPack hook with the @electron/fuses library to flip RunAsNode, EnableNodeOptionsEnvironmentVariable, and EnableNodeCliInspectArguments fuses to false.

Technical details

The vulnerability results from Electron's RunAsNode fuse being enabled in the build, which permits setting ELECTRON_RUN_AS_NODE=1 to execute arbitrary Node.js code within the JupyterLab Desktop process. An attacker with existing code execution in the user context can inherit previously granted TCC permissions (macOS Transparency, Consent, and Control), gaining unauthorized access to protected directories like Documents, Desktop, and Downloads without triggering additional OS prompts. This is a local privilege escalation requiring prior compromise; Windows and Linux builds are unaffected.

Affected products

Project Jupyter JupyterLab Desktop prior to 4.6.2-1 (macOS only)

Timeline

2026-11-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.