Skip to content
HighVulnerability

GHSA-24pw-rf5p-mgp7: Jupyter MCP Server: Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP mode

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

Standalone streamable-http mode in datalayer/jupyter-mcp-server requires MCP_TOKEN for /mcp, but the custom management routes on the same application do not enforce it. An unauthenticated network caller can call PUT /api/connect to set the Jupyter backend URL and token, reset the server context, and make the MCP server start a kernel client against attacker-controlled infrastructure. DELETE /api/stop, a state-changing route, is also unauthenticated.

Mitigation

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