CRITICALCVSS v4 9.3Vulnerability

CVE-2026-77359

Standalone `streamable-http` mode in `datalayer/jupyter-mcp-server` rejects forged `Host` and `Origin` headers on `/mcp`, but custom management routes mounted on the same application do not get the same browser-origin protection. A malicious website can keep an attacker origin while its hostname resolves to `127.0.0.1` or a private target address, then send `PUT /api/connect` to replace the MCP server's active Jupyter backend. The route accepts the browser-shaped request and makes the server start a kernel client against attacker-controlled infrastructure. The protected `/mcp` endpoint shows the intended browser-origin boundary. With `MCP_TOKEN` configured, `/mcp` rejects forged browser headers: ```text POST /mcp with Authorization: Bearer SCAN_MCP_TOKEN Host: attacker.example:8142 Origin: http://attacker.example:8142 HTTP 421 Invalid Host header ``` The vulnerable route is `jupyter_mcp_server/server.py:143-187`. It parses caller JSON, updates the active Jupyter backend configuration, resets `ServerContext`, and starts the kernel without applying the `/mcp` Host/Origin rejection to the custom route: ```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, runtime_token=document_runtime.runtime_token, document_url=document_runtime.document_url, document_id=document_runtime.document_id, document_token=document_runtime.document_token, allowed_jupyter_tools=document_runtime.allowed_jupyter_tools or "notebook_run-all-cells,notebook_get-selected-cell" ) ServerContext.reset() try: __start_kernel() return JSONResponse({"success": True}) ``` `/api/stop` is also state-changing and accepts the same browser-origin route shape: ```pytho

Properties

Summary
Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes
Severity
critical
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00503
Cvss score
9.3
Cvss severity
CRITICAL
Retrieved at
2026-11-22T12:32:28+00:00
Ghsa published
2026-11-20T00:12:51Z
Source url
https://github.com/advisories/GHSA-9x8x-crjq-g64h
Ghsa updated
2026-11-20T00:12:52Z
Ghsa id
GHSA-9x8x-crjq-g64h
Last source
FIRST EPSS
Score
9.3
Cvss version
4.0
Cve id
CVE-2026-77359
Cvss vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H/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-77359
Is ghsa only
false
Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H/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-77359 (CVSS v4 9.3) — Ninja Signal Threat Intelligence | Ninja Signal