Skip to main content
VulnerabilityPublished

CVE-2026-86044: jupyterlab-desktop · Open Redirect

Affects jupyterlab-desktopSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical : upgrade to 4.6.2-1 as a priority.

Data as of 6 Nov 2026, 20:50 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.6
Patch
Available – fixed in 4.6.2-1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade jupyterlab-desktop to 4.6.2-1.

Affected software

ProductAffectedFixed in
jupyterlabjupyterlab-desktopAffected
  • <4.6.2-1
Fixed in
  • 4.6.2-1

AI-suggested

Upgrade JupyterLab Desktop to version 4.6.2-1 or later, which includes the fix for this vulnerability. Users running version 4.4.8 or later are not affected by the initial redirect issue, but upgrading to 4.6.2-1 ensures full remediation. No other mitigation steps are indicated by the vendor advisory.

Description

JupyterLab Desktop versions prior to 4.6.2-1 contain an open redirect vulnerability (CWE-601) that allows an attacker to craft a malicious link in an untrusted notebook. When a user opens this notebook and clicks the link, the application navigates to an attacker-controlled site which can then access sensitive local server information and authentication tokens. This enables the attacker to use the Jupyter REST API to create and trust a notebook that executes arbitrary code as the victim. The vulnerability is fixed in version 4.6.2-1.

References

Community reviews

Loading reviews…