CVE-2026-77359 PUBLISHED

Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes

Assigner: GitHub_M
Reserved: 20.08.2026 Published: 19.11.2026 Updated: 19.11.2026

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.

Metrics

CVSS Vector: 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
CVSS Score: 9.3

Product Status

Vendor datalayer
Product jupyter-mcp-server
Versions
  • Version < 1.0.3 is affected

References

Problem Types

  • CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action CWE