AI Stack Alert High CVE-2026-77318 For AppSec, AI Eng, SOC / IR AI-assisted
Jupyter MCP Server before 1.0.3: unauthenticated /api/connect and /api/stop routes bypass MCP_TOKEN
Jupyter MCP Server prior to 1.0.3 enforces MCP_TOKEN on /mcp in standalone streamable-http mode but leaves the /api/connect and /api/stop management routes unauthenticated. An unauthenticated network caller can use /api/connect to replace runtime and document URLs and tokens, and can stop the current notebook kernel. The issue is fixed in version 1.0.3 and has a CVSS base score of 7.3.
Why it matters
Any network-reachable deployment in this mode can be pointed at attacker-controlled Jupyter backends, causing notebook traffic to be sent there. Attackers can also stop active notebook kernels without authentication.
Do this
- Upgrade Jupyter MCP Server to version 1.0.3 or later.
- Until patched, restrict network access to the streamable-http listener to trusted hosts only.
- Review logs for unexpected requests to /api/connect and /api/stop, and for unexpected runtime_url or document_url changes.
- Rotate Jupyter runtime and document tokens if unauthorized /api/connect calls are found.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 7.3CVSS
- NoPublic PoC
- 37/100Priority
- 85%Confidence
Evidence
“standalone streamable-http mode can enforce MCP_TOKEN on /mcp while leaving the state-changing /api/connect and /api/stop management routes unauthenticated”
“This issue is fixed in version 1.0.3.”
Sources
Affected / related
Jupyter MCP Server, Unauthenticated management route access
Published 2026-11-19 17:18 UTC · updated 2026-11-19 18:35 UTC · AI-assisted summary, checked against quoted sources · How we score