External risk intelligence

Jupyter MCP Server API Origin Validation Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-77359

The Jupyter MCP Server is primarily a developer-oriented tool used for connecting Model Context Protocol clients to Jupyter environments. While it can be configured for streamable-http mode which may be reachable from a network, it is not typically deployed as a public-facing internet service. Exposure is possible in specific deployment scenarios, but it is not a common internet-facing gateway or edge application.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in the Jupyter MCP Server, which is a tool for connecting Model Context Protocol clients to Jupyter environments. This issue could allow a malicious website to compromise the server by redirecting requests to an attacker-controlled infrastructure, potentially impacting notebook kernel operations. The primary concern is confirming if this specific technology is in use and exposed.

  • Attackers can redirect server requests.
  • It affects Jupyter's model context protocol.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could leverage DNS rebinding to trick a user's browser into connecting to a vulnerable Jupyter MCP server. By manipulating the browser's request, the attacker can then alter critical configuration settings, reroute Jupyter API and WebSocket traffic to their own infrastructure, and even shut down the notebook kernel. This allows the attacker to intercept and control parts of the Jupyter environment.

  • Attacker exploits DNS rebinding.
  • Malicious website triggers API routes.
  • Reroutes traffic, controls kernel.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a malicious website could leverage DNS rebinding to trick the Jupyter MCP Server into directing traffic, including API and WebSocket communication, to an attacker-controlled endpoint. This could allow an attacker to manipulate runtime and document URLs, potentially stopping active notebook kernels and rerouting sensitive data.

  • Jupyter MCP Server API and WebSocket traffic.
  • Malicious website via DNS rebinding.
  • Kernel control and traffic redirection.

Operational Fix

Recommended remediation, mitigation, and detection steps

Ownership of Jupyter MCP Server, particularly when deployed in streamable-http mode, likely falls to the platform or infrastructure teams responsible for the Jupyter environment. The first practical step involves identifying all instances of the affected server, assessing their reachability and criticality, and then coordinating remediation with the accountable owners to mitigate the risk of unauthorized kernel control.

  • Identify all instances and owners.
  • Verify internal/external reachability and impact.
  • Plan remediation based on risk assessment.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Jupyter MCP Server?

The Jupyter MCP Server is a component that enables the Model Context Protocol (MCP) for Jupyter environments. Developers use this server as a bridge to allow MCP-compatible clients to interact with Jupyter tools, facilitating data exchange and integration between external models and notebook environments.

What is the vulnerability class for CVE-2026-77359?

This vulnerability is classified as CWE-350: Remote File Authentication Bypass or, in this specific case, an improper restriction of origin-based requests. It means the server fails to verify that sensitive configuration commands are coming from a trusted source, allowing unauthorized requests to change critical server settings.

How can an attacker trigger this vulnerability?

An attacker uses DNS rebinding to trick a victim's web browser into communicating with a local or internal Jupyter MCP Server. The bug is not triggered by standard /mcp traffic, which is properly restricted; it occurs only when an attacker sends malicious requests specifically to the unprotected /api/connect or /api/stop management routes.

Do I need to worry if my Jupyter MCP Server is internal?

Yes, it is relevant regardless of network perimeter. According to Halo Surface Signal, while this server is not a typical public-facing gateway, it remains reachable via a user's browser if the server is accessible on a LAN, VPN, or within a container environment. The browser acts as a proxy for the attacker.

What is the recommended first step to address CVE-2026-77359?

Your first step is to locate all active installations of the Jupyter MCP Server in your environment. Once identified, verify if they are running a version prior to 1.0.3, specifically those utilizing streamable-http mode. Coordinate with your infrastructure teams to prioritize updating these instances to version 1.0.3 or later to secure the management routes.

References