Skip to content
A detailed explainer is available in Japanese. Read the Japanese explainer
Critical 9.3

Jupyter MCP Serverの接続先を奪う脆弱性、修正版あり

CVE-2026-77359 First seen on SecPulse

Summary

Jupyter MCP Serverの1.0.2以前に、悪意あるWebサイトからJupyterの接続先を攻撃者側へ差し替えられる脆弱性が公表されました。standalone streamable-httpモードで運用している組織は、1.0.3へ更新してください。

AI summary

Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.

Jupyter MCP Serverの1.0.2以前に、悪意あるWebサイトからJupyterの接続先を攻撃者側へ差し替えられる脆弱性が公表されました。standalone streamable-httpモードで運用している組織は、1.0.3へ更新してください。

Original description The description as published by the source.

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.

Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details