CVE Explore

Vulnerability in Datalayer Jupyter-Mcp-Server

CVE-2026-77359

CVSS
Not scored
Public exploits
1 repository
EPSS
0.005 · 43.9th percentile
Published
2026-11-19

What to do

Fixed in
1.0.3
Affected
1 affected product

Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode validates Host and Origin values for /mcp but does not apply the same browser-origin controls to the state-changing /api/connect and /api/stop management routes. A malicious website can use DNS rebinding so that its hostname resolves to a loopback, LAN, VPN, or published-container MCP listener, then send a browser-shaped request that /api/connect accepts to replace runtime_url and document_url values and start a kernel client against attacker-controlled infrastructure. The attacker can thereby cause Jupyter API and WebSocket traffic to reach that infrastructure and can use /api/stop to stop the current notebook kernel. The default broad bind can increase exposure, but the vulnerability is the missing management-route origin boundary, not a lack of Host validation on /mcp. This issue is fixed in version 1.0.3.

Published · last modified .

EPSS exploit prediction

EPSS 0.005, 43.9th percentile (last changed ). About EPSS.

Affected products

Weakness classification (CWE)

Public exploits and proof-of-concept code

1 public repository with exploit or proof-of-concept code for this CVE:

  • googlesky/CVE-2026-77359 (last pushed 2026-11-21): jupyter-mcp-server <=1.0.2: /mcp rejected forged Host/Origin but management routes didn't — DNS-rebinding website PUT /api/connect replaces the Jupyter backend (kernel hijack). Real server v1.0.2 vs…

References