Skip to content
Threat Brief

← All advisories

CVE-2026-77318

High 7.3No known exploitationFix available

Jupyter MCP Server: Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP mode

Vendor advisory: GHSA-24pw-rf5p-mgp7

Record last updated

CVSS score

7.3

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 44% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode can enforce MCP_TOKEN on /mcp while leaving the state-changing /api/connect and /api/stop management routes unauthenticated. An unauthenticated network caller can use /api/connect to replace runtime_url and document_url values and their tokens, reset ServerContext, and start a kernel client against attacker-controlled infrastructure, causing the server to send Jupyter API and WebSocket traffic to that backend. The caller can also use /api/stop to stop the current notebook kernel. This boundary failure does not require explicit insecure no-auth mode and occurs outside normal MCP JSON-RPC tool dispatch. This issue is fixed in version 1.0.3.

Weakness: CWE-306

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
datalayerjupyter-mcp-server< 1.0.3Not documentedCVE Program
pipjupyter-mcp-serverall versions up to and including 1.0.21.0.3GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references