Skip to main content
VulnerabilityPublished

CVE-2026-77359: datalayer jupyter-mcp-server · Reliance on Reverse DNS Resolution for a Security-Critical Action

Affects datalayer jupyter-mcp-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.0.3 as a priority.

Data as of 19 Nov 2026, 17:21 UTC

CVSS 4.0 base score
9.3Critical
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 4.09.3
Patch
Available – fixed in 1.0.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 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 18 Nov 2026.

What to do

Upgrade datalayer jupyter-mcp-server to 1.0.3.

Affected software

ProductAffectedFixed in
datalayerjupyter-mcp-serverAffected
  • <1.0.3
Fixed in
  • 1.0.3

AI-suggested

Upgrade jupyter-mcp-server to version 1.0.3 or later, where the missing origin validation on management routes /api/connect and /api/stop has been fixed. No additional mitigations are indicated by the vendor advisory.

Description

Jupyter MCP Server versions prior to 1.0.3 have a vulnerability where certain management API routes lack proper browser-origin validation. This allows a malicious website to exploit DNS rebinding to manipulate the /api/connect and /api/stop endpoints, potentially redirecting Jupyter API and WebSocket traffic to attacker-controlled infrastructure and stopping notebook kernels. The issue is fixed in version 1.0.3.

References

Community reviews

Loading reviews…