Auth bypass in Datalayer Jupyter-Mcp-Server
CVE-2026-77318
- CVSS
- Not scored
- Public exploits
- 1 repository
- EPSS
- 0.005 · 44.1th percentile
- Published
- 2026-11-19
What to do
- Fixed in
1.0.3- Affected
- 1 affected product
Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode can enforce MCP_TOKEN on /mcp while leaving the state-changing /api/connect and /api/stop management routes unauthenticated. An unauthenticated network caller can use /api/connect to replace runtime_url and document_url values and their tokens, reset ServerContext, and start a kernel client against attacker-controlled infrastructure, causing the server to send Jupyter API and WebSocket traffic to that backend. The caller can also use /api/stop to stop the current notebook kernel. This boundary failure does not require explicit insecure no-auth mode and occurs outside normal MCP JSON-RPC tool dispatch. This issue is fixed in version 1.0.3.
Vulnerability class: Broken Authentication
Published · last modified .
EPSS exploit prediction
EPSS 0.005, 44.1th percentile (last changed ). About EPSS.
Affected products
- Datalayer Jupyter-Mcp-Server — versions < 1.0.3
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- googlesky/CVE-2026-77318 (last pushed 2026-11-20): jupyter-mcp-server <1.0.3: standalone streamable-http management routes /api/connect and /api/stop skip MCP_TOKEN enforcement — an unauthenticated PUT resets the server context and points it at an at…