Skip to content
DayZeroHub
Critical CVSS 9.3GHSA-9x8x-crjq-g64hCVE-2026-77359

jupyter-mcp-server: DNS rebinding can redirect the Jupyter backend through management routes

datalayer jupyter-mcp-server

Summary

In jupyter-mcp-server's standalone streamable-http mode, custom management routes do not apply the Host and Origin protection that /mcp has. A malicious website could replace the server's active Jupyter backend. The source lists the fix in version 1.0.3.

What happened

In standalone streamable-http mode of datalayer/jupyter-mcp-server, the /mcp endpoint rejects forged Host and Origin headers. Custom management routes mounted on the same application do not get that browser-origin protection. According to the source, a malicious website can keep an attacker-controlled origin while its hostname resolves to 127.0.0.1 or a private address (DNS rebinding) and send a PUT request to /api/connect. That route accepts the browser-shaped request, replaces the MCP server's active Jupyter backend, and makes the server start a kernel client against attacker-controlled infrastructure. The /api/stop route, which also changes state, accepts the same kind of request. The weakness is classified as CWE-350.

Why it matters

The source assigns a CVSS 4.0 score of 9.3 (critical severity), with the 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. The described impact is that the MCP server can end up connected to an attacker-controlled backend. The source does not indicate known active exploitation: the vulnerability is not listed in CISA's KEV catalog.

Affected products and versions

jupyter-mcp-server (PyPI), versions <= 1.0.2. Fixed version: 1.0.3.

ProductVersionsFixed in
jupyter-mcp-server<= 1.0.21.0.3
datalayer jupyter-mcp-server< 1.0.3—

Action recommended by the source

The vendor lists the fix in jupyter-mcp-server version 1.0.3. The source links the v1.0.3 release, pull request 262, and a commit with the change. The source does not state any other mitigations.

Fixed in: 1.0.3

Information taken from the source or the vendor. Verify it at the original link before acting.

Sources and references

Weaknesses (CWE): CWE-350

Relevant change history

  1. Published

    Advisory published.

Summary written with AI assistance from the source data. See the sources and references for complete information. View sources