CVE-2026-77359

A browser could redirect Jupyter MCP through unguarded management routes

datalayer · Jupyter MCP Server · standalone streamable HTTP

First documented disclosure · Review checkpoint

Summary

A visited website could use DNS rebinding to change the Jupyter backend.

Severity and exploitation evidence

Critical · 9.3/10 · CVSS 4.0. Severity source.

Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Host/origin checks on /mcp did not cover state-changing management routes.

Conditions required

A visited malicious page can reach the local, LAN, VPN or container-published listener through DNS rebinding.

Potential impact

Kernel interruption and Jupyter traffic redirected to an attacker-selected backend.

Affected versions and configurations

Through 1.0.2.

Fix and mitigation status

1.0.3; confirmed by tagged server middleware despite stale advisory field Patched versions: None.

Practical next steps

Upgrade to 1.0.3 and keep MCP_TOKEN configured; verify management-route host/origin and token checks.

Operating lesson

Apply the same security boundary to management routes and the main protocol endpoint.

Evidence and limits

Original July advisory predates November 19 CNA ingestion. Tagged 1.0.3 installs ManagementRouteSecurityMiddleware, restricts management host/origin and checks bearer credentials on connect/stop when configured. The DNS-rebinding scenario requires visiting a malicious page despite the CNA CVSS 4.0 UI:N metric; both facts are retained. CNA publication is 2026-11-19; this is distinct from the earliest reviewed public source and correction dates. GitHub_M assessments: CVSS 4.0 9.3. Exact source checked: https://github.com/datalayer/jupyter-mcp-server/blob/v1.0.3/jupyter_mcp_server/server.py. The July 11 release predates the July 12 DNS-rebinding advisory; its release is not relabeled as a new November fix.

Sources