Skip to main content
CVE-2026-77318VulnerabilityPublished

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

Affects jupyter-mcp-serverSource GCVE Database

0
Compare
Authoritative record:CVE-2026-77318· High 7.3

Not known to be exploited · CVSS 7.3 High : upgrade to 1.0.3 soon.

Data as of 20 Nov 2026, 01:48 UTC

CVSS 4.0 base score
7.3High
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.07.3
Patch
Available – fixed in 1.0.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:H/SI:H/SA:L

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

Upgrade to version 1.0.3 or later, where these management routes enforce proper authentication. Until then, restrict network access to the MCP server to trusted clients only. The vendor advisory confirms a patch is available in version 1.0.3.

Description

The Jupyter MCP Server in standalone streamable-http mode enforces authentication via MCP_TOKEN on the /mcp endpoint but fails to enforce this token on custom management routes such as /api/connect and /api/stop. This allows unauthenticated attackers to reset the server context, redirect the Jupyter backend to attacker-controlled infrastructure, start kernel clients, and stop notebook kernels without authentication. The vulnerability is fixed in version 1.0.3.

References

Community reviews

Loading reviews…