Skip to main content
VulnerabilityPublished

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

Affects jupyter-mcp-serverSource GCVE Database

0
Compare
Authoritative record:CVE-2026-77359· Critical 9.3

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.0.3 as a priority.

Data as of 20 Nov 2026, 01:38 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.09.3
Patch
Available – fixed in 1.0.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 evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade jupyter-mcp-server to 1.0.3.

Affected software

ProductAffectedFixed in
PyPIjupyter-mcp-serverAffected
  • <1.0.3
Fixed in
  • 1.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Jupyter MCP Server version 1.0.3 that fixes this vulnerability by enforcing browser-origin protections on all management routes. Users should upgrade to version 1.0.3 or later. Until patched, restricting access to the MCP server to trusted networks and disabling exposure to untrusted browsers can reduce risk.

Description

Jupyter MCP Server versions prior to 1.0.3 contain a vulnerability where custom management routes do not enforce the same browser-origin protections as the main /mcp endpoint. This allows a malicious website to perform a DNS rebinding attack, sending crafted requests to internal MCP server routes such as /api/connect and /api/stop. These routes accept forged Host and Origin headers, enabling an attacker to replace the active Jupyter backend configuration and control kernel execution. The vulnerability is fixed in version 1.0.3.

References

Community reviews

Loading reviews…