Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| datalayer | jupyter-mcp-server | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Datalayer | Jupyter-mcp-server |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9x8x-crjq-g64h | Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.503% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Datalayer
Datalayer jupyter-mcp-server |
|
| Vendors & Products |
Datalayer
Datalayer jupyter-mcp-server |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode validates Host and Origin values for /mcp but does not apply the same browser-origin controls to the state-changing /api/connect and /api/stop management routes. A malicious website can use DNS rebinding so that its hostname resolves to a loopback, LAN, VPN, or published-container MCP listener, then send a browser-shaped request that /api/connect accepts to replace runtime_url and document_url values and start a kernel client against attacker-controlled infrastructure. The attacker can thereby cause Jupyter API and WebSocket traffic to reach that infrastructure and can use /api/stop to stop the current notebook kernel. The default broad bind can increase exposure, but the vulnerability is the missing management-route origin boundary, not a lack of Host validation on /mcp. This issue is fixed in version 1.0.3. | |
| Title | Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes | |
| Weaknesses | CWE-350 | |
| References |
|
|
| Metrics |
cvssV4_0
|