Answer in brief
CVE-2026-77318 records a High severity (CVSS 7.3) vulnerability in Jupyter MCP Server: Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP mode. The current sources do not mark it as known exploited. The current feed maps datalayer/jupyter-mcp-server (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps datalayer/jupyter-mcp-server (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| datalayer/jupyter-mcp-servergeneric | <1.0.3 | 1.0.3 |
Published upstream
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.