Back to feed
21Track

datalayer jupyter-mcp-server: Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter…

datalayer jupyter-mcp-server · CVE-2026-77359 ETK-2026-4953
0 news outlets0 CERTs and agencies1 research labs

Assessment: Track

SSVC decision points: exploitation none, automatable yes, technical impact partial, deployment low.

What is it?

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.

Evidence

Technical advisories1Detailed write-ups from security research teams

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
9.3
EPSS
–
First seen
1 h ago
Status
confirmed

All datalayer vulnerabilities