GPU VulnDB

Database/AI/ML frameworks & serving

Jupyter MCP Server: unauthenticated /api/connect and /api/stop routes redirect or stop the kernel

CVSS 7.3CVE-2026-77318AI/ML frameworks & servingcurated

Impact

Before 1.0.3, standalone streamable-http mode can enforce MCP_TOKEN on /mcp but leave the state-changing /api/connect and /api/stop routes open. An unauthenticated caller can use /api/connect to swap the runtime and document URLs and their tokens, reset the server context, and point the kernel client at infrastructure the attacker controls, so Jupyter API and WebSocket traffic from the agent goes to that backend. The caller can also stop the current notebook kernel through /api/stop. This happens even when insecure no-auth mode was never turned on, so an operator who set a token may believe the server is protected.

Who can reach it

Anyone who can reach the Jupyter MCP Server's HTTP port in standalone streamable-http mode. No authentication needed.

What to do

Upgrade jupyter-mcp-server to 1.0.3 and restart the server. Until then, do not expose the streamable-http port beyond trusted clients.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.