AI Stack Alert Critical CVE-2026-77359 For SOC / IR, AppSec, AI Eng, CISO AI-assisted
CVE-2026-77359: Jupyter MCP Server before 1.0.3 lacks origin checks on /api/connect and /api/stop
Jupyter MCP Server prior to 1.0.3 validates Host and Origin for /mcp in standalone streamable-http mode but not for the state-changing /api/connect and /api/stop routes. A malicious website using DNS rebinding can send a browser-shaped request that /api/connect accepts, replacing runtime_url and document_url values and starting a kernel client against attacker-controlled infrastructure. The issue is fixed in version 1.0.3.
Why it matters
Organizations running Jupyter MCP Server in streamable-http mode, especially on loopback, LAN, VPN, or published-container listeners, can have notebook traffic redirected and kernels stopped by a visiting browser. The source reports a CVSS base score of 9.3.
Do this
- Upgrade Jupyter MCP Server to version 1.0.3 or later.
- Until patched, run standalone streamable-http mode only on trusted networks and avoid broad bind addresses.
- Restrict or block access to the /api/connect and /api/stop routes at a reverse proxy or host firewall.
- Review logs for unexpected /api/connect requests that change runtime_url or document_url, and for unexpected kernel stop events.
- Audit published-container and VPN exposure of MCP listeners.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 9.3CVSS
- NoPublic PoC
- 43/100Priority
- 80%Confidence
Evidence
“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.”
“This issue is fixed in version 1.0.3.”
Sources
Affected / related
Jupyter MCP Server, DNS rebinding
Published 2026-11-19 17:18 UTC · updated 2026-11-19 18:35 UTC · AI-assisted summary, checked against quoted sources · How we score