Jupyter MCP Server: DNS rebinding hijacks Jupyter backend via management routes (CVE-2026-77359)
Severity: critical · Patch status: patched · Since 2026-11-20 · CVE-2026-77359
jupyter-mcp-server's standalone streamable-http mode checks Host and Origin on /mcp, but before 1.0.3 its custom management routes, /api/connect and /api/stop, did not run those checks. A web page can use DNS rebinding so the browser keeps an attacker origin while the hostname resolves to 127.0.0.1 or another address the MCP listener answers on. The page can then send PUT /api/connect, which replaces the server's Jupyter runtime and document URLs and tokens, so the server sends Jupyter API and WebSocket traffic, including the supplied tokens, to attacker-run infrastructure. DELETE /api/stop can stop the current kernel. Exposure requires --transport streamable-http: the default transport is stdio, which is not affected. In that mode the listener binds 0.0.0.0, so loopback, LAN and published containers are all reachable targets. MCPTOKEN does not protect these routes before 1.0.3. Fixed in 1.0.3, which applies Host and Origin checks to the management routes. The advisory publishes a full reproduction transcript; no in-the-wild exploitation is reported.
What to do
- Upgrade jupyter-mcp-server to 1.0.3 or later immediately. The current PyPI line is 2.2.x; its tags carry the same management-route middleware plus a local-peer check
- Keep the default stdio transport unless streamable-http is required. Only streamable-http is affected
- If an upgrade is not possible, block the MCP port at the host firewall and do not publish it from Docker. Versions 1.0.2 and 1.0.3 hardcode the bind to 0.0.0.0, so loopback-only binding is not a configuration option there
- Check logs for unexpected PUT /api/connect or DELETE /api/stop requests and for connections to unknown runtime_url or document_url hosts
- Rotate any runtime or document token the server held while it was reachable from an untrusted page
- Until upgraded, do not browse untrusted sites in the same browser while streamable-http mode is running
Fixed versions
Sources
All live incidents on Threat Watch