Skip to content
CriticalVulnerability

GHSA-9x8x-crjq-g64h: Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes

Published
Record updated
View JSON
Affected
  • jupyter-mcp-server <= 1.0.2
Fixed in
1.0.3
  • released July 11, 2026, 132 days before disclosure
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.

Summary

The standalone streamable-http mode of datalayer/jupyter-mcp-server rejects forged Host and Origin headers on /mcp, but custom management routes such as PUT /api/connect and DELETE /api/stop lack that browser-origin protection. A malicious website can use DNS rebinding to send PUT /api/connect, replacing the server's active Jupyter backend and causing it to start a kernel client against attacker-controlled infrastructure. The proof of concept was run against commit 27b91e551d8bbca2da32c334f9f13267290ff815 with MCP_TOKEN configured.

Mitigation

The source does not state a fix yet. Check the original advisory for updates.