CVE Feed
9.3 Critical

Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes

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 MCPTOKEN configured, /mcp rejects forged browser headers: text POST /mcp with Authorization: Bearer SCANMCPTOKEN Host: attacker.example:8142 Origin: http://attacker.example:8142 HTTP 421 Invalid Host header The vulnerable route is jupytermcpserver/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.customroute("/api/connect", ["PUT"]) async def connect(request: Request): data = await request.json()…

Part of the AI stack

This affects Jupyter, Model Context Protocol, in MCP & tool servers, Apps & interfaces.

Assessment

CVSS
9.3 (v4.0)
Severity
Critical
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
20 November 2026
Last updated
20 November 2026
Weakness
CWE-350

CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-77359