---
title: "CVE-2026-77359: Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes"
url: https://erroneo.us/security/cve/CVE-2026-77359/
description: "CVE-2026-77359 (jupyter-mcp-server (PyPI)): Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-11-19
date_modified: 2026-11-20
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-77359"
kev: false
cvss: 9.3
epss: 0.00503
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-77359: Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.5% , percentile 44: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 44% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes jupyter-mcp-server (PyPI) <= 1.0.2, fixed in 1.0.3 . Check your lockfile, including transitive dependencies.

## What it is

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 runtimeurl and documenturl 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.

## Affected packages

- PyPI `jupyter-mcp-server` <= 1.0.2 → fixed: 1.0.3

## Affected products (CVE record)

- datalayer jupyter-mcp-server: < 1.0.3

## Severity

- GitHub_M CVSS 4.0: 9.3 `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`
- GitHub CVSS 4.0: 9.3 `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`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable yes , technical impact partial .
- FIRST EPSS (model of 2026-11-21): 0.50% probability of exploitation activity in the next 30 days; percentile 44.

## Sources

- [GitHub Advisory GHSA-9x8x-crjq-g64h](https://github.com/advisories/GHSA-9x8x-crjq-g64h)
- [CVE.org record CVE-2026-77359](https://www.cve.org/CVERecord?id=CVE-2026-77359)
- [NVD entry CVE-2026-77359](https://nvd.nist.gov/vuln/detail/CVE-2026-77359)
- [github.com](https://github.com/datalayer/jupyter-mcp-server/security/advisories/GHSA-9x8x-crjq-g64h)
- [github.com](https://github.com/datalayer/jupyter-mcp-server/pull/262)
- [github.com](https://github.com/datalayer/jupyter-mcp-server/commit/c2e98fca2df1bbd608451ec416aaa38a4)
- [github.com](https://github.com/datalayer/jupyter-mcp-server/releases/tag/v1.0.3)

---
Source page: https://erroneo.us/security/cve/CVE-2026-77359/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt
