GPU VulnDB

Database/AI/ML frameworks & serving

Jupyter MCP Server: management routes lack origin checks, letting DNS rebinding redirect or stop kernels

CVSS 9.3CVE-2026-77359AI/ML frameworks & servingcurated

Impact

In standalone streamable-http mode, Host and Origin are checked on /mcp but not on the /api/connect and /api/stop management routes. A malicious website can use DNS rebinding to reach the listener through a user's browser and rewrite runtime_url and document_url. The server then sends Jupyter API and WebSocket traffic, including notebook content and kernel execution, to infrastructure the attacker controls. The same route trick can stop the running notebook kernel, killing long GPU sessions. The default broad bind widens exposure to LAN, VPN and published-container listeners.

Who can reach it

Unauthenticated and remote, but it needs a user whose browser can reach the MCP listener (loopback, LAN, VPN or a published container port) to visit a page the attacker controls.

What to do

Upgrade jupyter-mcp-server to 1.0.3 or later and restart the MCP server process. Until then, bind it to loopback only and do not publish its port from containers.

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.