HIGHCVSS v4 7.3Vulnerability

CVE-2026-77318

Standalone `streamable-http` mode in `datalayer/jupyter-mcp-server` requires `MCP_TOKEN` for `/mcp`, but the custom management routes mounted on the same application do not enforce that token. An unauthenticated network caller can invoke `PUT /api/connect`, choose the Jupyter backend URL and token fields, reset the server context, and make the MCP server start a kernel client against attacker-controlled infrastructure. The same missing authentication affects the state-changing `DELETE /api/stop` route. The intended authentication boundary is documented in the security guide and enforced during startup: ```text docs/docs/reference/security/index.mdx:15 All MCP endpoints require Bearer token authentication. docs/docs/reference/security/index.mdx:25 Starting with version 1.0.0, MCP client authentication is required for the streamable-http transport. ``` The CLI enforces that boundary for the MCP endpoint: ```python # jupyter_mcp_server/CLI.py:203-209 if transport == "streamable-http" and not mcp_token and not insecure_mcp_noauth: raise click.UsageError( "streamable-http transport requires MCP client authentication. " "Set --mcp-token / MCP_TOKEN, or pass --insecure-mcp-noauth to " "explicitly allow unauthenticated access." ) ``` ```python # jupyter_mcp_server/CLI.py:285-290 if transport == "streamable-http": if mcp_token: from jupyter_mcp_server.server import RuntimeTokenVerifier mcp._token_verifier = RuntimeTokenVerifier(mcp_token) logger.info("MCP endpoint token authentication enabled (using MCP_TOKEN)") ``` The vulnerable route is `jupyter_mcp_server/server.py:143-187`: ```python @mcp.custom_route("/api/connect", ["PUT"]) async def connect(request: Request): data = await request.json() document_runtime = DocumentRuntime(**data) set_config( provider=document_runtime.provider, runtime_url=document_runtime.runtime_url, runtime_id=document_runtime.runtime_id,

Properties

Summary
Jupyter MCP Server: Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP mode
Severity
high
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00505
Cvss score
7.3
Cvss severity
HIGH
Retrieved at
2026-11-22T12:32:28+00:00
Ghsa published
2026-11-20T00:12:14Z
Source url
https://github.com/advisories/GHSA-24pw-rf5p-mgp7
Ghsa updated
2026-11-20T00:12:16Z
Ghsa id
GHSA-24pw-rf5p-mgp7
Last source
FIRST EPSS
Score
7.3
Cvss version
4.0
Cve id
CVE-2026-77318
Cvss vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
First seen by Signal
2026-11-19T19:29:21+00:00
Name
CVE-2026-77318
Is ghsa only
false
Vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Related Entities (3)

AFFECTS (1)

VULNERABLE_TO (1)

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-77318 (CVSS v4 7.3) — Ninja Signal Threat Intelligence | Ninja Signal